Declare the canonical URL in every RIP preamble - #5
Merged
Conversation
RIP-0001 has carried both fields in its preamble since the governance split (95c135c, 2026-07-07). RIP-0002 through RIP-0011 carried neither, so a copy of any of them said nothing about where its original is published. Both are added to the ten remaining RIPs, in the position RIP-0001 uses and with the values it uses: License: CC0-1.0 Canonical-URL: https://rips.rincoin.org Repository: https://github.com/Aevust/rincoin-rips Canonical-URL is the site root rather than a per-RIP address. What the field has to survive is a document being rehosted, and the root does that without binding eleven files to a URL layout that may change. Repository is included because it is the field a fork cannot copy without contradicting itself. Neither field appears in RIP-0001 §Header Preamble, which specifies the format every RIP MUST follow. RIP-0001 uses both regardless, so the specification is behind the practice of the document that defines it. Aligning §Header Preamble with what RIP-0001 already does is a separate change on a gated path, and belongs with the §Repository Structure correction tracked for the same file. Four lines in rip-0010 and rip-0011 also lose trailing whitespace, stripped by the editor on save. None are Markdown hard breaks: each ends a paragraph already followed by a blank line, or pads a line that was otherwise blank. Nothing renders differently. They are left in rather than split out because separating four rendering-neutral characters would cost more history than it explains. Updated is left alone in all ten. §Header Preamble ties that field to substantive revision, and nothing normative in these documents changed.
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.
One commit, ten files. Every RIP now declares where its original is
published and which repository is canonical for it.
RIP-0001 has carried both fields since the governance split
(95c135c, 2026-07-07). RIP-0002 through RIP-0011 carried neither.
A copy of any of those ten, rehosted anywhere, said nothing about
where the original lives — the reader had to already know.
Both are added in the position RIP-0001 uses, directly after
License:Canonical-URLis the site root rather than a per-RIP address. Whatthe field has to survive is a document being rehosted, and the root
does that without binding eleven files to a URL layout that may
change.
Repositoryis included because it is the field a forkcannot carry without contradicting itself: a copy served from
elsewhere that still names this repository is visibly a copy.
No status, no specification wording, and no
Updateddate changes.§Header Preamble ties
Updatedto substantive revision, and nothingnormative in these ten documents changed. Four lines in
rip-0010and
rip-0011lose trailing whitespace, stripped by the editor onsave; none are Markdown hard breaks, so nothing renders differently.
What this does not settle
RIP-0001 §Header Preamble specifies the fields a RIP preamble MUST
contain, and neither field is among them. RIP-0001 uses both anyway,
so the specification is behind the practice of the document that
defines it. This pull request extends the practice; it does not amend
the specification, and it does not claim authority it lacks —
/rip-0001/is gated, and the amendment goes through that path.That amendment is worth batching.
rip-0001§Repository Structurelists
security/*_public.ascwhile the file issecurity/aevust.asc,already tracked for the same path. Two corrections to §Header Preamble
and §Repository Structure are one review rather than two.
Checks
rip-checkverifies that eachrip-NNNN/directory contains amatching
rip-NNNN.md; it does not inspect preambles. No pathchanges here, so it passes unchanged. Markdown is outside CodeQL's
supported languages, and the known Warning-level alert on
rip-check.yml— it declares nopermissionsblock — predates thispull request and sits below the Errors threshold.
Out of scope
SECURITY.mdhas no preamble and gains no field here. A laterchange describing which documents carry
Canonical-URLshould nameGOVERNANCE.mdand the RIPs rather than "governance documents".rip-0004andrip-0011carrySee-Also, andrip-0009andrip-0010carryRelated— likewise absent from §HeaderPreamble. Same gated path, same batch.
fix(ci): restrict GITHUB_TOKEN permissions in rip-check.