Skip to content

docs(planning): architecture/ promotion ships in the implementing PR#106

Merged
lesnik512 merged 1 commit into
mainfrom
docs/architecture-promotion-in-branch
Jun 20, 2026
Merged

docs(planning): architecture/ promotion ships in the implementing PR#106
lesnik512 merged 1 commit into
mainfrom
docs/architecture-promotion-in-branch

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Follow-up to #105. The single-step lifecycle eliminated post-merge bookkeeping, but the convention prose still described the architecture/ promotion ambiguously ("updated whenever a change ships", "promoted from a change on merge") — readable as a separate after-merge step.

Makes it explicit in both planning/README.md and CLAUDE.md: the architecture/<capability>.md promotion is a hand-edit that rides in the implementing PR's diff, alongside the code, and is reviewed with it — never applied after merge. It is the one ship-time step (no folder move, no status flip done separately).

Docs-only; no code or behavior change.

🤖 Generated with Claude Code

… not on merge

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@lesnik512 lesnik512 merged commit b36b516 into main Jun 20, 2026
3 checks passed
@lesnik512 lesnik512 deleted the docs/architecture-promotion-in-branch branch June 20, 2026 10:23
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