Development record
2026-09-29 — The 2026-09-29 entry applying ruling J15 names one plain-path consequence of the ledger forgetting a stopped domain, a domain edited out of `rules.json` and back; there is a second, which needs no edit at all: a dormant domain activated with `*NAME` is in force for that prompt alone, so a prompt without the prefix drops it from the active set and the next `*NAME` renders it again (review-routerRemoval finding 2; recorded by fix round fix-routerRemoval of autonomous run A; Refs: iss-2608261550580260). Both follow from J15, since the domain left the set in between, and both are documented in brief `05-internals/03-configuration.md` "The prompt router's output"; the rule-loader text in `AGENTS.md` and the managed-repository marker block qualify "never re-injects unchanged rules" to a domain that stays in force. The earlier entry stands as written.
2026-09-29 — The 2026-09-29 entry applying ruling J15 names one plain-path consequence of the ledger forgetting a stopped domain, a domain edited out of rules.json and back; there is a second, which needs no edit at all: a dormant domain activated with *NAME is in force for that prompt alone, so a prompt without the prefix drops it from the active set and the next *NAME renders it again (review-routerRemoval finding 2; recorded by fix round fix-routerRemoval of autonomous run A; Refs: iss-2608261550580260). Both follow from J15, since the domain left the set in between, and both are documented in brief 05-internals/03-configuration.md "The prompt router's output"; the rule-loader text in AGENTS.md and the managed-repository marker block qualify "never re-injects unchanged rules" to a domain that stays in force. The earlier entry stands as written.
Frontmatter
| id | dcn-2609290000000015 |
|---|---|
| type | decision |
| date | 2026-09-29 |
.abcd/work/decisions/dcn-2609290000000015-the-2026-09-29-entry-applying-ruling-j15.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608261550580260The prompt-router emits only domains whose content changed this turn, so a client that snapshots injected rules — a host-side adaptor staging them into a system prompt, or a future MCP consumer — keeps a domain that was deleted or renamed mid-session until session end: there is no removal signal in the protocol. Emit the full active-domain-name set, or tombstones for removals, so a snapshotting client can prune. A local second-harness adaptor lab hit this and had to accept the lingering snapshot as a recorded gap.