The several-accounts intent asks the fork question once per process at a drain's start; the reserve chapter asks it at each drain lane's reservation, not at the start, and asks a failed question again after a minute.

The several-accounts intent asks the fork question once per process at a drain's start; the reserve chapter asks it at each drain lane's reservation, not at the start, and asks a failed question again after a minute.

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

• End A: .abcd/development/brief/04-surfaces/37-reserve.md:262 — "Each drain lane asks at its own reservation, through that cache, not once at the drain's start."
• End B: .abcd/development/intents/shipped/itd-2610161016394967-several-people-each-on-their-own-github.md:110 — "a fresh reservation and a drain start ask the forge once per process whether origin is a fork, and refuse one; renewals never ask"

itd-2610161016394967 records that a fresh reservation and a drain start ask the forge once per process whether origin is a fork, and that renewals never ask. 37-reserve.md has each drain lane ask at its own reservation, through a cache, and says this is not done once at the drain's start. It also holds a failed question for only a minute before asking again, and has a drain's renewal of its own lapsed reservation ask as a fresh one does. The two documents give different counts and moments for the same network act.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The 'once per process at a drain's start' line is the planning-time decision that the delivered spec step narrowed, and the same record says so.