Development record
itd-37 puts append-only pages into .abcd/memory/; universal pattern § 8 gives each namespace one lifecycle class and lists .abcd/memory/ as compounding-curated
itd-37 puts append-only pages into .abcd/memory/; universal pattern § 8 gives each namespace one lifecycle class and lists .abcd/memory/ as compounding-curated
A sequencing impossibility (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/disciplines/itd-37-modification-grammar.md:63— "Writes append-onlyspec_modification_grammar_<spec_id>.mdto.abcd/memory/withsource.class: spec_modification_grammar." - End B:
.abcd/development/brief/05-internals/04-universal-patterns.md:188— "Lifecycle class is declared in the parent README of each artefact namespace."
itd-37 writes append-only per-spec pages into .abcd/memory/, beside a compounding-curated per-domain page, and cites § 8 for both lifecycles. 04-universal-patterns § 8 declares one lifecycle class per artefact namespace in its parent README, lists .abcd/memory/ as compounding-curated, and has lint block a namespace whose behaviour disagrees with its class. One namespace cannot hold both of itd-37's classes under that taxonomy.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 823.
Frontmatter
| id | iss-2610262038511722 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262038511722-itd-37-puts-append-only-pages-into-abcd.md
open on GitHub ↗ · commit history ↗
References1
- itd-37Every Spec Externalises How It Should And Shouldn't Be Modifiedrelated