redgate

The ARM stage of Red Gate: turn an interviewed idea into CRITERIA.md and check.sh in .redgate/<slug>/, prove the gate red (every checkable criterion FAIL, harness preflight clean), get human ratification, and pin the sha256 of both files into the run manifest. Use at the start of every redgate round; never write code before this gate is red and ratified.

The JUDGE stage of Red Gate: verify a round from a context that did not do the work. Refuse an unratified run, re-hash both pinned artifacts and fail on drift, run the pinned verifier yourself, accept a PASS only with evidence written this run, then apply the mutation control. Use to close any redgate round, and never let the writer grade its own work.

Default protocol for nontrivial work needing explicit criteria or evidence. Compose it around the most-specific applicable specialist skills rather than replacing them. Auto-trigger for planning, research, design, implementation, debugging, refactoring, review, deployment, multi-agent coordination, and external/irreversible actions when the work needs verified rounds or a classified human gate. Handle trivial work directly; route larger work through ARM/TRACE/JUDGE. Use the harness-native structured question primitive when available and compact textual choices otherwise; never emit prose questionnaires.