itd-2609212130146198 has the guard refuse a question while the mode reads managed; the board's surface page has the guard admit abcd's chipped question and set the state from it.

itd-2609212130146198 has the guard refuse a question while the mode reads managed; the board's surface page has the guard admit abcd's chipped question and set the state from it.

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/shipped/itd-2609212130146198-the-status-line-badge-is-true-at-every.md:40 — "a question to the human through the host's question tool is refused while the mode reads managed"
• End B: .abcd/development/brief/04-surfaces/08-abcd.md:172 — "guard hook, on the host's question tool, admits abcd's own question"

The badge intent says a question to the human through the host's question tool is refused while the mode reads managed, and that the mode verb sets the state. 08-abcd.md says the guard hook admits abcd's own question headed in the chip grammar, sets the state from the chip's role itself, and that a chipped question is never refused on the mode; it also has the answer reset the state through the question tool's PostToolUse hook, not only on the next prompt. A chipped question asked while the mode reads managed is refused under one and admitted under the other.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 538.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. guard_question.go lets a chipped question through whatever the mode reads.