forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
2d58779675
rev-974 found this while loading the canonical gate sources, i.e. because we switched from restating to reading. Verified in roles.local/merge-gate.md: mandate 3 requires verifying 'CI queue guard clear', mandate 4 requires enumerating 'the queue-guard outcome' in every durable verdict, the merge path annotates it 'real', and the control table at :290 certifies it '✅ enforced … genuinely aborts'. The document is correct about the WIRING and wrong about the CONTROL: set -euo pipefail with an unguarded exit does abort, but the guard cannot produce a non-zero exit for any input (D-23). A mechanism correctly wired to a sensor that never fires, certified as enforced. Compounding: the verdict format REQUIRES the queue-guard outcome as evidence, so a conforming verdict must include a meaningless field — the role file instructs the gate to manufacture evidence, in the mandate that exists to stop bare conclusions. Interim: record the field labelled ZERO-INFORMATION (inert, owner RM-03) rather than omitting it — omission makes the verdict non-conforming; silent citation is worse. Escalated: operator-owned file, coordinator's to fix. Recommend annotation not deletion — the requirement is correct once RM-03 lands. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>