AI is my high-throughput implementation layer, not the authority. Work moves from a written spec to tests, implementation, and an independent second-model review. Risky claims go to adversarial panels whose job is to refute them; release claims name the exact gate and commit that passed.
The process has killed a lookahead leak, a pairing flaw that could have promoted a worse strategy, and a prompt-injection bypass before merge. The reusable skeptic panel is open source as refute. Durable constraints live in repo-native playbooks and decision ledgers, not in a model's memory.
Evidence before exposure
paper → shadow → canary → live, with preregistered endpoints and kill thresholds where the claim needs them.
Adversarial review
Independent critics attack the spec, code, evidence, and visual result. A review that cannot reproduce its claim does not move the score.
Guarded operation
Preview→execute boundaries, spend caps, recoverable state, and fail-closed fallbacks contain the damage when a provider or model is wrong.