Development record
itd-39 reuses the rules loader's context brackets (itd-3); the configuration chapter's loader has no context brackets and attributes the budget bracket to itd-39 itself
itd-39 reuses the rules loader's context brackets (itd-3); the configuration chapter's loader has no context brackets and attributes the budget bracket to itd-39 itself
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-39-scope-aware-memory-retrieval.md:75— "Memory recall uses the rules loader's context brackets (itd-3); there are no thresholds tuned separately for memory." - End B:
.abcd/development/brief/05-internals/03-configuration.md:1174— "but keyword recall with a budget bracket (itd-39)"
itd-39 rules that memory recall uses the rules loader's context brackets, with no thresholds of its own. The configuration chapter's account of the loader and the prompt router has a per-session dedup and a fixed 64 KiB injection budget, and no bracket tied to remaining context. Its one mention of a bracket credits it to itd-39 ('keyword recall with a budget bracket (itd-39)'). Each document assigns the brackets to the other, so neither one builds what itd-39 depends on.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 868.
Frontmatter
| id | iss-2610262039330569 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262039330569-itd-39-reuses-the-rules-loader-s-context.md
open on GitHub ↗ · commit history ↗
References1
- itd-39abcd Surfaces the Right Memory at the Right Momentrelated
mentions2
- iss-2610262044561718itd-39 reuses the rules loader's context brackets from itd-3, but itd-3's loader defines no brackets
- itd-3abcd Loads Its Own Rules On Demand