docs: make specs/plans git-tracked and transient — retired via git rm at cycle close

docs/specs and docs/plans hold only the active cycle's artefacts: a spec/plan is committed while its cycle is live and git-rm'd in the cycle-close commit (after audit drift-clean), so HEAD shows only in-flight work while git history keeps the full text. No issue-posting, no gitignore branch — git history + the design ledger are the durable record. Rewrites conventions.md § Lifecycle as the single source of truth; pipeline.md, design.md, README.md, specify, planner, glossary, brainstorm, issue, and the CLAUDE.md fragment follow it. Naming stays NNNN-slug.md (a within-cycle handle; recycling on an emptied directory is fine).
2026-06-18 11:59:45 +02:00
parent c5da79f8fc
commit 012e70b058
10 changed files with 68 additions and 13 deletions
@@ -87,6 +87,11 @@ standing reading (`CLAUDE.md` + `git log -10`), git discipline
 (only-orchestrator commits, main sacrosanct), Gitea + `closes #N`,
 and the whole pipeline graph (see `pipeline.md`).

+Specs and plans are ephemeral active-cycle artefacts — the two
+directories stay git-tracked and hold only what is in flight; at cycle
+close each is `git rm`'d from the repo, kept only in git history, never
+as a durable file (see `conventions.md` § Lifecycle).
+
 ## Project facts (project-specific)

 The handful of facts that genuinely vary per project live in the