The folder-classification intent calls ahoy's registry of managed repositories "the history store"; in the history chapter that store is the transcript store, kept apart from the registry.

The folder-classification intent calls ahoy's registry of managed repositories "the history store"; in the history chapter that store is the transcript store, kept apart from the registry.

A naming conflict (severity nitpick) found by the cross-document consistency pass.

• End A: .abcd/development/intents/shipped/itd-40-folder-classification.md:16 — "the history store's index.json keyed on each repo's root-commit SHA"
• End B: .abcd/development/brief/04-surfaces/11-history.md:15 — "ahoy's registry stays under ~/.abcd.noindex/history/ and holds no transcripts."

itd-40 names the machine-wide registry of managed repositories the history store's index.json, under a scope heading "The history-store registry". The history chapter makes the history verb's store the session-transcript store under transcripts/<root-sha>/records/. It says ahoy's registry under history/ holds no transcripts, and that install provisions the registry, not the store. The one name "history store" therefore stands for two different stores.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The registry file is still index.json in the history folder (internal/core/ahoy/store.go) while the history verb's store is the separate transcripts tree, so the later chapter simply sharpens a name itd-40 used loosely.