Skip to content

docs(specs): spec lifecycle — ledger, precedence rule, delete-on-ship - #78

Merged
nmccready merged 1 commit into
mainfrom
docs/spec-lifecycle-ledger
Jul 15, 2026
Merged

docs(specs): spec lifecycle — ledger, precedence rule, delete-on-ship#78
nmccready merged 1 commit into
mainfrom
docs/spec-lifecycle-ledger

Conversation

@nmccready

Copy link
Copy Markdown
Contributor

Codifies the completed-spec cleanup convention:

  • specs/README.md — permanent ledger, back-filled for every SPEC ID ever used (001–008): status, retire commit, where durable content lives in docs/. IDs stay resolvable after spec bodies are deleted.
  • .agents/rules/specs.md (always_on) — precedence: docs/ + code are current truth, specs never outrank them; fully-shipped specs are promoted into docs and deleted in the same PR (git history is the archive — no specs/completed/ graveyards); partially-shipped specs get trimmed to open work.
  • docs/README.md retired-specs note now points at the ledger; AGENTS.md regenerated.

🤖 Generated with Claude Code

…ete-on-ship

- specs/README.md: permanent ledger back-filled for SPEC-001..008
  (status, retire commit, durable-doc destinations); lifecycle steps
- .agents/rules/specs.md (always_on): docs/ and code are current truth;
  specs never outrank them; ship → promote to docs + delete + ledger row;
  no specs/completed graveyards
- docs/README.md: point the retired-specs note at the ledger
- AGENTS.md regenerated (sync-agents index)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

🤖 AI Code Review

✅ Clean review — no findings. (model: deepseek/deepseek-v4-flash)

model: deepseek/deepseek-v4-flash · est. cost: $0.0003

@nmccready
nmccready merged commit c9edc21 into main Jul 15, 2026
6 checks passed
@nmccready
nmccready deleted the docs/spec-lifecycle-ledger branch July 15, 2026 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant