skills/kb-bootstrap/assets/vault/00_System/Document Lifecycle.md.tmpl

---
type: governance
project: {{PROJECT_YAML}}
status: active
---

# Document lifecycle

Project notes carry `type`, `project` and `status`. Canonical domain notes also
identify `domain`, `feature`, `canonical`, `owner` and evidence/validation state.
Keep lifecycle (`draft`, `review`, `active`, `temporary`, `deprecated`,
`superseded`, `archived`) separate from the evidence supporting individual claims.

- Current notes describe current truth. Review dates trigger inspection, not expiry.
- Preserve durable accepted rationale in a decision record, not every routine edit.
  Use a unique `DEC-YYYY-NNN` ID after checking the current records/index; decision
  numbering is a shared edit that must be serialized between agents.
- Mark replaced records with `superseded_by` or `replacement` and remove them from
  active indexes. Retain valuable history. Do not delete ambiguous historical data.
- Pending work belongs in [Backlog](Backlog/Index.md); execution belongs in
  [Work](Work/Index.md). Move completed work into its Archive and update active routes.
- Keep historical notes outside the default startup route. Use the installed
  `kb-maintenance` workflow at milestones and when stale or conflicting knowledge
  appears. The lint profile at the KB root defines the actual mechanical scope.

No background maintenance scheduler is installed by these rules.