Four flows, one rule: the human judges, the engine measures

Discovery — you bring the idea, the method proposes the shape

The skill explores first, then asks one question at a time — each with a recommended answer. You confirm or correct; you never author the shape from a blank page. The package is written to the repo as decisions crystallize.

Reverse Discovery — extract facts, then quarantine the claims

The running system's behavior is the truth. The skill extracts facts (map, golden), then authors candidates in quarantine — never specs. The old rule "never author an inferred spec" was renegotiated in ADR-009: you may author candidates, you may never promote them without a verdict.

INV-GOLDEN-01 is enforced mechanically on Claude Code (a blocking PreToolUse hook); on every other target the kit reports it as advisory — the measured control everywhere is golden-diff, which compares bytes.

Curation — one human verdict, everything else measured

This is the differentiator. A candidate is machine-validated; a candidate with no verdict blocks the PR, naming itself (INV-CURATION-01). The single human decision splits into three buckets. A fix declares its expected divergence, which the golden oracle then checks. roundtrip reports traceability by id — advisory, never a gate.

Compile, certify, round-trip — the forward leg the three flows feed

The curated package becomes a typed graph. Any model compiles it; the engine only validates the output contract and never compiles. A withheld oracle — authored before any compilation, never in the prompt — certifies whether the result is the same system. Then the reverse organs try to re-anchor the asset from the compiled code, and that ratio is published with its ceiling.