Development record
itd-39 names a 'workspace' memory scope; the ahoy chapter says abcd has no workspace layer, only the repository and the user scope
itd-39 names a 'workspace' memory scope; the ahoy chapter says abcd has no workspace layer, only the repository and the user scope
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/01-ahoy.md:547— "There is no workspace, host, or development-environment layer." - End B:
.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md:35— "On a recall-keyword conflict, the narrower scope wins (workspace > user)."
itd-39 queries memory across two scopes, the workspace and the user's personal store, and <workspace>/.abcd/memory/ wins a conflict over the user scope. The ahoy chapter says abcd manages exactly one kind of folder, a repository, plus one user-scope directory. It says there is no workspace, host or development-environment layer, and that a folder grouping repositories gets no special treatment. Calling the narrower scope 'workspace' either names the repository with a word the brief rules out or implies a layer the brief says does not exist.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 374.
Frontmatter
| id | iss-2610262033126804 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033126804-itd-39-names-a-workspace-memory-scope.md
open on GitHub ↗ · commit history ↗
References1
- itd-39abcd Surfaces the Right Memory at the Right Momentrelated