Problem
Decisions have no lifecycle. Once written, they exist forever unless manually pruned by age. Status-based archival ('archive all Implemented entries') is impossible because there's no Status field.
From
Flight review of #20 (section 3.3), EECOM review (status-based archival).
Proposed States
proposed → active → implemented → superseded → archived
Changes Needed
- Add
status field to ParsedDecision type in domain-types.ts
- Update
parseDecisionsMarkdown() to extract **Status:** X from entry body
- Update
archiveDecisions() to archive implemented entries regardless of age
- Update Scribe charter: when merging inbox, default status =
active
- Agents instructed to set
Status: Implemented when shipping related work
Owner
EECOM (Core Dev) + Procedures (Prompt Engineer)
Problem
Decisions have no lifecycle. Once written, they exist forever unless manually pruned by age. Status-based archival ('archive all Implemented entries') is impossible because there's no Status field.
From
Flight review of #20 (section 3.3), EECOM review (status-based archival).
Proposed States
proposed→active→implemented→superseded→archivedChanges Needed
statusfield toParsedDecisiontype in domain-types.tsparseDecisionsMarkdown()to extract**Status:** Xfrom entry bodyarchiveDecisions()to archiveimplementedentries regardless of ageactiveStatus: Implementedwhen shipping related workOwner
EECOM (Core Dev) + Procedures (Prompt Engineer)