ENGINEERING NOTES
Problems worth explaining properly.
Short technical notes on the evidence boundaries, failure modes and design decisions behind the systems I build.
NOTES
Four recurring debugging traps.
A config file does not tell you what an AI agent is actually running
Why declared configuration, resolved effective state and live observations need separate evidence.
Why a route dump does not explain a Linux routing decision
Policy routing, multiple tables and why the running kernel should stay the routing oracle.
Static dependencies and runtime causality are different questions
Why configuration references and incident reconstruction need separate evidence models.
What Postfix status=sent actually proves
How to stop an email-delivery verdict at the last confirmed stage instead of guessing inbox placement.