itd-39's hook queries a user-scope memory store at ~/.abcd.noindex/memory/; the library chapter lists user-scope memory outside the repo as not built.

itd-39's hook queries a user-scope memory store at ~/.abcd.noindex/memory/; the library chapter lists user-scope memory outside the repo as not built.

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

• End A: .abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md:35 — "the hook queries the index.md of both memory scopes (<workspace>/.abcd/memory/ and ~/.abcd.noindex/memory/)"
• End B: .abcd/development/brief/04-surfaces/07-library.md:415 — "user-scope memory outside the repo"

itd-39 (planned) has the prompt hook query the index of both memory scopes, the workspace .abcd/memory/ and ~/.abcd.noindex/memory/, with the narrower scope winning, and its decisions say release placement no longer waits because itd-36's store has shipped. 07-library's account of what ships lists user-scope memory outside the repo under Not built, and the store it documents lives in the repo at .abcd/memory/ alone. Nothing in itd-39's scope builds the second scope, so its two-scope query depends on a store no record delivers.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): the two ends do not conflict when read in full. spc-2610111627213138 (Scopes, step 3) makes the machine-scope page read optional ('when it exists'), so the two-scope query does not depend on a store being delivered; 07-memory.md and 07-library.md consistently call the user-scope store a later phase.