governance: no rfc: issue during 0.x; the RFC comes back at the v1.0 freeze or with a second implementation - #15
Merged
Conversation
…omment window; the RFC comes back at the v1.0 freeze, or earlier the day a second implementation is listed (closes #8) The reference implementation is today the only producer and consumer, so a comment window protects no one. The pull request still states the SPEC.md diff and the migration impact, and CHANGELOG.md records the change as breaking. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
During the 0.x draft line, a breaking change no longer needs an
rfc:issue or a 14-day comment window. The editor merges it with a MINOR bump, which §6 already allows during 0.x.Why: a comment window protects implementers that a change would break. Today the reference implementation is the only producer and consumer of MetaLog documents, so the window protects no one and only delays a correction the editor has already decided.
What is kept. The pull request still states the change as a diff against
SPEC.mdand gives its migration impact (items 2 and 4 of an RFC issue).CHANGELOG.mdrecords it as breaking in the same pull request. Only the wait is dropped, not the record.The RFC comes back, and the editor cannot waive it.
rfc:issue and the Process at 1.0+ column.README.md's implementation table. From then on a breaking change can break someone other than the editor. ADR 0001's first freeze condition requires a second implementation, so this always happens before the freeze.Files
GOVERNANCE.md:CONTRIBUTING.md: the process step points at §2 instead of an unconditional RFC process.CHANGELOG.md(0.10.0, unreleased): records that RFC rfc: 0.10.0 — close the extension boundary, make the diff's MUST decidable, and give the composed document its own caps #8 is closed. P2 already landed in 0.10.0. P1, P3 and P4 remain proposed, and any that is taken lands as an editor change recorded there.conformance/metalog_validate.py --selftestpasses 31/31. No schema orSPEC.mdtext changes, so no document's validity moves.Closes #8.
🤖 Generated with Claude Code