Robustness Audit & Preflight Validation

The doctrine's deterministic backstop

The design doctrine and pattern library shape what an agent is likely to build; they don't guarantee it. A deterministic robustness audit runs over an authored graph as an enforcement layer independent of whatever the synthesis model actually produced — catching a missing fallback, an ungated irreversible action, or an unbounded fan-out even if the model that drafted the graph forgot the doctrine entirely.

Preflight catches starved inputs before a single node runs

Validation is layered ahead of that: graph reference checks, expression safety (workflow conditions and transforms are parsed by a hand-written safe expression parser — never eval), graph normalization, and a reachability lint that specifically catches a node whose required input can never actually arrive given the graph's real wiring. Finding that at build time, instead of watching a run stall waiting on an input that was never going to come, is the entire point of preflight.

Continue