Sam Moore

Many carrier tools are paywalled and look like they were designed in 2004. I built the one I wished I had on my route, and other carriers started asking for updates the same week I shipped them: grievance calendar math, route forward tracking, per-carrier color themes, because real accessibility requests came in, a verifiable privacy mode I can screenshot.

Built with experience guiding design, every feature is driven by someone at a case who told me what they needed.

Route knowledge walks out the door with every retirement. Decades of which box sits behind which bush, which dog is on which porch, which nuance data point. Retainment of new people is at an all time low. I built a wiki the older carriers are not afraid to touch and the new hires can actually search.

It is also the precursor to doing anything useful with a local LLM later. A real database is a prerequisite for retrieval augmented anything.

Off-the-shelf controllers did not fit the room, and the ones that came close wanted a subscription to tell me the temperature. So I engineered the bridge myself. Redundant sensors feeding an aggregator that ignores the offline one. Cron for what happens on a schedule. Dynamic thresholds for what does not. Time series out to a dashboard so I can see when the room is lying to me.

Normalization across redundant sensors prevents a single hardware failure from cascading into bad decisions downstream. Low-tech insight. Cost almost nothing.

My in-laws are aging into technology they cannot troubleshoot. I am building a hardened appliance I can remote into, patch, and reason about from my own house. Motion, contact, environmental, and eventual glass-break sensors. Home Assistant as the orchestration layer. Tailscale tunnel so there are no open inbound ports at their place.

The final shape lives in industrial enclosures. It should look like it belongs in a utility closet, not a college dorm. The goal is their autonomy and my peace of mind. Those two metrics matter more than any efficiency gain.