016-bounded-active-specs
Active specifications stay bounded and historical journals stay outside the corpus
Lifecycle approvedImplementation completeVerification unknownQualification unknown
Amends spec 001's authoring model so an active spec carries current requirements and concise resolved rationale, never an append-only work log. A mechanical gate bounds active files and moves historical journals and handoffs to a nonnormative archive outside the compiler input.
Read the full pinned specification ↗Relationships
depends on
depended on by
Claimed units
- establishes
{ "kind": "file", "path": "scripts/check-spec-corpus.sh" } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "scripts/check-authored-content.sh" } }
Source headings
- 016: Active specifications stay bounded
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Active content and historical content are different records
- 3.2 One active file per spec directory
- 3.3 Mechanical budgets
- 3.4 The normal governance gate runs the check
- 4. Out of scope
- 5. Resolved decisions
- Verification
Frozen anchors
No frozen anchors declared.