Skip to content

docs(rfc): distinguish lifecycle from delivery maturity #5348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
huangruiteng merged 1 commit into from
Sep 30, 2026
Merged

docs(rfc): distinguish lifecycle from delivery maturity #5348

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture/rfcs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,7 @@ failure leaves the generated files untouched.
- [Shared Goal Alignment and Governed Amendment Protocol v0](shared-goal-alignment-and-governed-amendment-v0.md)
([中文版](shared-goal-alignment-and-governed-amendment-v0.zh-CN.md))
- **Delivery on `main`:** Stage 1/2 read-only alignment and proposal-admission
foundations implemented; the RFC remains a draft.
foundations implemented; Stage 3+ remains unshipped.
- **Current boundary:** Current Todo/lease source-basis projection and retained
amendment admission have no canonical effect. Full Goal-intent versioning,
governed commit policy/verifier, lease-impact handling and Stage 3+
Expand Down
6 changes: 6 additions & 0 deletions docs/architecture/rfcs/TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,12 @@ answer), and a `Superseded` RFC must link its successor that reciprocally names
its predecessor. Normative checkpoint persistence/recovery headings and
historical appendix records are legal.

`Delivery maturity: Proposal` means that implementation has not shipped; it
does not make an Accepted RFC a draft. In the README's delivery column, name
the implemented slice and remaining delivery boundary. Keep lifecycle state
in the canonical header and generated index rather than describing a merged
active RFC as Draft or Under review in delivery prose.

---

## 1. Decision summary
Expand Down
Loading