Repository navigation
Plan statuses: every plan uses the process's five words, and CI keeps it so #1027
Description
development-process.md and docs/plans/TEMPLATE.md give a plan five statuses: draft, approved, active, complete, abandoned. in-progress and chartered were retired on 2026-09-21 (NobleFactor/noblefactor-ops#219). devlore-cli's plans do not hold to them, and nothing checks: its CI runs no frontmatter gate over docs/plans.
Inventory of the 349 files under docs/plans, 2026-10-04:
| State | Files |
|---|---|
| Status is exactly one of the five words | 215, 32 of them corrected 2026-10-04 from in-progress and chartered |
| One of the five words, with commentary or the wrong case | 53 |
Outside the vocabulary: proposed, charter — …, IMPLEMENTED, SHIPPED, settled, closed, completed, ready, pending, deferred, design-solidified, done pending commit |
23 |
| No frontmatter, no status | 49 |
| No frontmatter, a status elsewhere | 8 |
TEMPLATE.md, frontmatter without a status |
1 |
One file, extract-starlark-from-op/phase-8/lore-migration.md, has a blank line ahead of its frontmatter.
The fix
- Every plan carries frontmatter whose
statusis exactly one of the five words. The plan rules the commentary, each value outside the vocabulary, and the files without frontmatter. - CI fails a plan whose status is outside the vocabulary, with the base layer's
Test-Frontmatter.sh, the organization's reference implementation (documentation-standards.md).
Done when
- Every file under
docs/planscarries frontmatter whosestatusis exactly one of the five words - CI fails a plan whose status is not
- The pull request says so, with the gate's output as the proof
Plan and design documents
| Kind | Document |
|---|---|
| Plan | docs/plans/chore/1027-plan-statuses-every-plan-uses.md |
Epic: NobleFactor/noblefactor-ops#142 · Feature: NobleFactor/noblefactor-ops#156 · Schedule: #916, lane 45, PR C
Activity
docs(plan): #1027's plan, every plan uses the process's five statuses…