Development record
The configuration chapter has the binary read a prompt-counting refresh backstop; the verification matrix says nothing counts prompts.
The configuration chapter has the binary read a prompt-counting refresh backstop; the verification matrix says nothing counts prompts.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/05-internals/03-configuration.md:93— "prompt-router refresh backstop (itd-3). The primary refresh is" - End B:
.abcd/development/brief/06-delivery/02-verification-matrix.md:73— "Nothing counts prompts"
03-configuration lists rules.force_refresh_every_n (15) as a hand-set key the binary reads, a refresh backstop that re-injects always-relevant domains on a counter. The verification matrix's dedup row says the refresh is event-driven rather than turn-counted and nothing counts prompts. A shipped counter-based re-injection and no prompt counting at all cannot both be true.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 782.
Frontmatter
| id | iss-2610262038154778 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262038154778-the-configuration-chapter-has-the-binary.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610262040213900The memory chapter gives the prompt router a refresh every N prompts; the verification matrix says the refresh is event-driven and nothing counts prompts.
- itd-3abcd Loads Its Own Rules On Demand