Skip to content

docs(specs): retire the plan of spec 027 - #112

Merged
plainprogrammer merged 2 commits into
mainfrom
027-retire-plan
Oct 15, 2026
Merged

plainprogrammer merged 2 commits into
mainfrom
027-retire-plan

Conversation

@plainprogrammer

@plainprogrammer plainprogrammer commented Oct 15, 2026 •

Copy link
Copy Markdown
Owner

Follow-up to #110 (spec 027, merged at f831bf2): spec 027's index row read "retirement owed". This retires its plan using the distill-feature after-merge procedure, the same way 015 and 024 were retired in #110.

  • c1ef5f0 deletes docs/specs/027-architecture-area-docs/plan.md and changes nothing else.
  • The next commit points to it (spec 027 D4):
    • the spec header gets the line **Plan:** retired in `c1ef5f0138c6898ab171fe6315281e6fed5c86c2`; read it with `git show c1ef5f0138c6898ab171fe6315281e6fed5c86c2^:docs/specs/027-architecture-area-docs/plan.md`
    • the plan link in verification.md line 3 becomes plain text
    • the index row changes to Status Shipped (it was Approved) and Plan retired, with the pointer

Checks: git show c1ef5f0^:docs/specs/027-architecture-area-docs/plan.md prints the plan, and git show --stat c1ef5f0 lists only the deleted plan. The existing pointers for 015 and 024 resolve (git cat-file -e). bin/ci passes (1507 examples, 0 failures).

Merge with a merge commit, not squash or rebase. The pointer names c1ef5f0, a commit on this branch, so it has to stay in main's history (docs/git-convention.md, Merging).

🤖 Generated with Claude Code

plainprogrammer and others added 2 commits October 15, 2026 14:39
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@plainprogrammer
plainprogrammer marked this pull request as ready for review October 15, 2026 18:53
@plainprogrammer plainprogrammer self-assigned this Oct 15, 2026
@plainprogrammer
plainprogrammer merged commit a0eeaab into main Oct 15, 2026
4 checks passed
@plainprogrammer
plainprogrammer deleted the 027-retire-plan branch October 15, 2026 18:54
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