Read it left to right: the method governs · the tool executes · evidence decides · the human approves
1 · The method governs
• Before code, a spec skill interviews you and writes the contract: ADRs + ACCEPTANCE (the criteria).
• New idea: discovery. Known feature: adr-refine. Old system: reverse-discovery + characterize.
• A design with state and rules is model-checked first (TLA+).
2 · The tool executes
• The agent builds against the contract and runs the review loop (devloop).
• A review tier set by the changed paths (quick · standard · deep) picks the review tools; the engine hands each one its scope, and every finding names path:rule.
• Hooks stop what the agent must never do, like writing an approved golden.
3 · Evidence decides
• The engine records only measured runs; it never takes the agent's word.
• Coverage says a line ran; mutation testing (PIT, pit-check) says whether a test would catch it changing.
• The gate reads the ledger: tests current, acceptance green, every located finding fixed or deferred, every tier tool's clean pass current.
• Readouts show the same numbers; they never compute their own.
4 · The human approves
• You decide the spec, approve the goldens, and approve the merge.
• Only a human lowers a review tier or confirms a deferral.
• The agent cannot declare 'done': the gate does, from evidence.
Architecture diagram • Press T for theme and E for export