itd-140's gate hardens once itd-139's fixture exists; the dashboard intent replaced itd-139 and gave the genericity promise up

itd-140's gate hardens once itd-139's fixture exists; the dashboard intent replaced itd-139 and gave the genericity promise up

A sequencing impossibility (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/disciplines/itd-140-the-generic-specific-boundary-of-the.md:57 — "hardens once itd-139's fixture instance exists"
• End B: .abcd/development/intents/planned/itd-2610032150577708-a-product-thinker-opens-abcd-s-dashboard.md:47 — "give up the promise. The record site and the dashboard are promised for abcd's own record only; itd-140 carries the ruling."

itd-140's armed-detector rung waits on itd-139's fixture instance, which it names as the genericity demonstration. itd-2610032150577708 rules that the dashboard replaces itd-139 and that the record site is promised for abcd's own record only, saying itd-140 carries that ruling, which itd-140 as written does not. The rung waits on a record that will not be built.

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