I build software, electronics and infrastructure. Usually the interesting part is where they meet.
- RuntimeTruth — compares Codex runtime settings, permissions and instruction files with a reviewed baseline. It can also verify signed baselines. Source · PyPI
- PowerContract — checks oscilloscope CSV captures against electrical limits and timing requirements written in YAML. Source · PyPI
- HA Blast Radius — finds Home Assistant entity references before a rename or removal. Source
- HA Forensic Lab — records Home Assistant events and saves incident timelines for debugging. Source
- MailForensics — traces outbound email through application logs, Postfix, filters and relays. Source · PyPI
- route-explain — shows which route Linux selects for a flow and the rules and tables involved. Source · PyPI
RuntimeTruth and PowerContract are published under Sidelobe.
- Checking power-up timing against a datasheet — why comparing scope captures with electrical requirements still often means writing custom scripts.
- AI agent configuration at runtime — how to check the settings Codex actually resolves, not just what a config file says.
- Debugging Linux policy routing — start with a kernel route lookup, then inspect the rules and tables behind it.
- Home Assistant dependencies and state changes — why finding configuration references and tracing an event are separate jobs.
- What Postfix
status=sentmeans — why acceptance by a relay is not proof of inbox delivery.