Align review scope with the ratified text - #3
Merged
Conversation
CODEOWNERS gated five paths. Only two of them are bound by any ratified provision. The remaining three were configuration choices that the text does not support, and two of them conflict with it. Gate retained, and anchored: /GOVERNANCE.md @ysmreg @Aevust /rip-0001/ @ysmreg @Aevust GOVERNANCE.md §Authority and Amendment binds amendments to these two documents to the same process, submission discipline and recording requirements. Nothing else in the ratified text imposes review on this repository: §Change Submission Discipline and Emergency Exception binds the official Rincoin Core repository, and SECURITY.md classifies this one as a Development repository. The leading slashes are a fix, not cosmetic. Without them the patterns follow gitignore semantics and match at any depth, so rip-0005/governance/ and doc/SECURITY.md would have been captured. Gate removed: - SECURITY.md. RIP-0001 §RIP Editors states that this file is updated independently of the RIP, expressly so that key rotation does not require amending it. Gating it defeated a stated design goal of the text it claimed to enforce. - governance/. GOVERNANCE.md obliges core-role.md to be updated whenever an assignment changes, and its Succession section operates precisely when the Founder is unavailable. A file that MUST be written in a reviewer's absence cannot require that reviewer's approval. The same applies to editor-changes.md, which Vacancy Determination and Succession both require to be written as those procedures run. The gate rendered ratified obligations unsatisfiable by configuration. It also verified the wrong thing. core-role.md records assignments; it does not create them. An entry is legitimised by the authorizing act under GOVERNANCE.md — a signed deputy designation, a recorded Core Strategic Authority decision, a Succession step — not by a review approval. Review of the record cannot substitute for the authority the record reports. - .github/CODEOWNERS. Gating this file behind the review it configures makes the configuration unrecoverable whenever review stalls. Its protection is this signed and reasoned commit, and the fact that every rule below it restates a ratified clause. No file other than .github/CODEOWNERS is touched. This narrows configuration to match the ratified scope. It amends no provision and confers no authority.
The Change Submission Discipline and Emergency Exception section was relocated from RIP-0001 to GOVERNANCE.md on 2026-07-07, as recorded in that file's Extracted-From header. core-role.md still cites it as RIP-0001 §Change Submission Discipline and Emergency Exception, and no such heading exists in rip-0001.md, so the citation does not resolve for a reader who follows it. Repoints the citation to GOVERNANCE.md and notes that the document is incorporated into RIP-0001 by reference, so the normative basis stated elsewhere — in SECURITY.md, in llms.txt and in the signed certificate — is unchanged by the move. Refreshes Last Updated, which still read 2026-06-07 and predates the relocation. Verified unchanged against GOVERNANCE.md: the mandatory pull request for the official Core repository, the emergency exception's scope and its bar on MAJOR/GENERATION increments, the 72-hour retroactive review, disclosure in governance/emergency-actions.md, the emergency authority holders, the distinct voter count of 2, and the 2/2 unanimity requirement for MAJOR. No assignment, voter count, or authority statement changes.
This was referenced Jul 22, 2026
Closed
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.
Two commits, kept separate for auditability.
chore(governance): derive the review gate from the ratified textCODEOWNERS gated five paths; only two are bound by any ratified provision. Narrows to
/GOVERNANCE.mdand/rip-0001/, and anchors both patterns. Founder review is removed fromSECURITY.md,governance/and.github/CODEOWNERS. The reasoning for each removal is in the commit message, and each rests on a clause of the ratified text rather than on a judgment call.docs(governance): repoint core-role.md to GOVERNANCE.mdThe Change Submission Discipline and Emergency Exception section moved to GOVERNANCE.md on 2026-07-07, as recorded in that file's
Extracted-Fromheader.core-role.mdstill cited it as a RIP-0001 section, and no such heading exists inrip-0001.md, so the citation did not resolve for a reader who followed it. Two lines changed: the citation and theLast Updatedfield.No provision is amended, and no authority is conferred by either commit.
Ruleset change applied alongside this PR
Ruleset changes leave no trace in git history, so this section is the record.
Removed. The scope was
~ALL, and thecreationandupdaterules blocked every branch and therefore every pull request — including any pull request that would have corrected the ruleset.required_linear_historywas required while merge commits were the only permitted method; those two cannot both be satisfied. The scope now narrows to~DEFAULT_BRANCH, and all three rules are dropped.Retained.
deletion,non_fast_forward,required_signatures, the pull request requirement, therip-checkstatus check withstrict_required_status_checks_policy, and the CodeQL code scanning requirement at theErrorsthreshold.bypass_actorsstays empty. Merge commits remain the only permitted method, so the author's signatures on the individual commits are preserved rather than rewritten.On
rip-check. It was reported asexpectedand never ran, because its workflow triggers onpull_requestwhile the pushes it appeared to block were direct pushes tomain. The check is implemented and passes here, though its current scope is therip-NNNN/rip-NNNN.mdfile layout only; validation of RIP-0001 §Header Preamble and §File Format remains to be added. The fault was in the push path, not in the check, and this ruleset closes that path.On code scanning. The CodeQL rule was blocked because no analysis had ever run: the rule requires results for both the pull request head and the target branch. CodeQL default setup was enabled during this pull request, and it analyses the GitHub Actions workflows under
.github/, so it is retained rather than removed. This pull request was closed and reopened once, so that analysis would run against its head commit after the setup was enabled. The one alert raised —actions/missing-workflow-permissionsonrip-check.yml— is a warning below theErrorsthreshold and is addressed in a separate pull request, to keep this one to the two files it describes.Sequencing
require_code_owner_reviewisfalsewhile this pull request is open, and is enabled immediately after it merges. It cannot be enabled first: the CODEOWNERS currently onmainassign.github/CODEOWNERSandgovernance/to the Founder, so the setting blocks the very change that narrows it. Enabling it beforehand was attempted and produced exactly that deadlock.Approval therefore moves from a flat count of one to code-owner review once merged, after which the scope in
.github/CODEOWNERSgoverns which paths need the Founder.On the pending review request
Ysmreg is requested automatically, because the CODEOWNERS on
mainassigns him those paths. The request remains open and is not dismissed by merging. Neither commit amends a provision or confers authority, and both are a single revert away. Any objection can be raised afterward and acted on.