itd-2609091416304128 treats 'the default branch' as refs/remotes/origin/main; 34-build defines it as origin's HEAD, falling back to main, master, trunk, then develop.

itd-2609091416304128 treats 'the default branch' as refs/remotes/origin/main; 34-build defines it as origin's HEAD, falling back to main, master, trunk, then develop.

A terminology drift (severity nitpick) found by the cross-document consistency pass.

• End A: .abcd/development/intents/drafts/itd-2609091416304128-capture-resolve-refuses-a-record-the.md:35 — "The verb reads the ledger at refs/remotes/origin/main through git's object store"
• End B: .abcd/development/brief/04-surfaces/34-build.md:599 — "cut from the default branch (origin's HEAD as last fetched, else the first of main, master, trunk and develop)"

The draft promises a refusal when the default branch has already closed the record, but reads only origin/main. In a repository whose default branch is master or trunk, it would carry on as if there were no upstream ref, while 34-build's definition would find that repository's real default branch. The draft uses the term more narrowly than the brief defines it.

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