The compilation table is the work plan
The design’s Part IV is a sixteen-row table, each row a piece of doctrine that exists as prose and the executable it becomes — work-order discipline into an intake linter, eval-first design into an exit gate, silence monitoring into watchdog jobs, germline discipline into branch protection and a changelog lint. That table is the construction plan of the factory; each row is documented on the Operations page of the station that runs it, starting at Station 0. Nearly every row is boring engineering — schemas, hooks, cron, CI. That is the point. The factory’s originality is in its theses; its construction is deliberately dull, because boring technologies are easier for agents to model — including the agents who maintain the factory.What compiling buys
A rule that cannot fail a build is a suggestion. A rule that fails a build is culture with a compiler:- Inspectable — the standard is the script; read it and you know exactly what is enforced.
- Improvable — culture changes arrive as diffs, reviewed and versioned like any code, under germline control.
- Honest — compliance is measured by exit codes, not by self-report.