Verify a gate with the adversary
Gate: the one being verified (L0-understand to L10-lessons). The builder never grades its own work.
- Fix the inputs: the gate id, the feature id, the project folder, the repository, the commit SHA under review and the artifacts of the gate. Do not hand the checker the builder's summary or reasoning.
- Choose the checker from
gatesin batuta.json:batuta:adversary(sonnet) for routine gates;batuta:reviewer(opus) for a critical gate (L2-decide, L5-freeze, L9-promote by default) and for a critical unit. - Write and lint its brief with the
briefskill (the evidence pathspecs/<feature>/evidence/<gate>.mdis its only write), then launch it with thedelegateskill:subagent_type="batuta:adversary"or"batuta:reviewer", model fromroute show. - Check the evidence file the agent wrote (verdict PASS, FAIL or PASS-WITH-FIXES; commands with output; a findings table):
python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" gate evidence-lint specs/FEATURE/evidence/GATE.md - Check the agent's report against the brief:
python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" report check --brief BRIEF - Re-run one or two of its load-bearing commands yourself before you rely on it.
- On PASS, record the gate (it is a dry run until you add
--apply, which writes the status):python "${CLAUDE_PLUGIN_ROOT}/scripts/batuta.py" gate status FEATURE --set GATE=passed - On FAIL or PASS-WITH-FIXES, the builder fixes every finding and this skill runs again on the new commit. Never waive a finding yourself; a waiver is a human's dated line.
On a non-zero exit: exit 1 from evidence-lint means the evidence is invalid (a claim without command and output, a
wrong role or model): send it back, the gate stays open. Exit 1 from gate status --set refuses the pass: read the reason.
Exit 2 is a warning: report it and do not treat the gate as passed.