Layer 04 · The gate
Verification
Every diff meets the same gates. Any failure blocks. There is no warning tier.
Layer 04 · Verification
What the agents do
- Run the gates on every diff: documentation, types, lint, format, tests, build.
- Repair what is mechanically repairable — a moved selector, a stale reference — and re-run.
- Prove the run is reproducible: seeded replay, a fixed as-of time, golden outputs.
What the machine refuses
- A single type, lint, format or test failure. There is no warning tier to hide in.
- A release with an ungrounded step — the citation check exits non-zero.
- A fabricated success state, a mock latency, an invented metric.
Where a person signs
Owns the reference sets
The golden outputs and reference data the checks compare against are curated by a person, so an agent is never grading its own work. Who checks the checker is the first question a sceptic asks; this is the answer.
Check it: This site: six blocking CI stages. A red run deploys nothing.
Methods
- Static code and schema guards
- Tests pass before merge
- Claim and citation enforcement
- Build-blocking policy violations
- Deterministic merge pipeline
- Seeded replay and golden outputs
The other layers