release(canon): 2.0.3 — the 0-canon district, law moved out of the repo root - #823
Merged
Merged
Conversation
…po root
Executes the 0-canon district of standards-map.toml, which is the spec: the map
is the agreed target layout and GATE D verifies the result bidirectionally. The
law stops living at the repository root.
Moves
constitution/ -> 0-canon/constitution/ (19 files)
CANONICAL-NAMES.adoc -> 0-canon/
COMPLIANCE-DASHBOARD.adoc -> 0-canon/
CRG-SELF-ASSESSMENT.adoc -> 0-canon/
GOVERNANCE.adoc -> 0-canon/
PORT-REGISTRY.adoc -> 0-canon/
RSR-PHILOSOPHY.adoc -> 0-canon/
TEMPLATE-APPLICABILITY-POLICY.adoc -> 0-canon/
References rewritten in the same commit, because a move with no reference
rewrite is a broken link. `standards-map.toml` `from` values now record the
migration as done.
WHY THIS IS A PATCH AND NOT THE "NO BUMP" RELOCATION THE LOCK ALREADY DOCUMENTS
The 2026-09-17 entry above took the escape route because the moved files were
BYTE IDENTICAL: "every sha256 below is UNCHANGED. ... The canon's identity is
its hash set, and that is identical." That escape is not available here. ALL
FIVE sha256 below changed, because the law names paths inside itself:
* template-capability-gates.toml lists "constitution/" among the paths that
define the canon, names TEMPLATE-APPLICABILITY-POLICY.adoc as `policy`,
and resolves GOVERNANCE.adoc as an alternative in governance-tier;
* those references were rewritten when the files moved, so the bytes are not
identical, so the identity is not identical, so there IS a new release
identity for the spine to adopt.
The obligation therefore fires and the rule's own menu gives the category. No
criterion is added, removed, re-tiered or re-gated; the architecture text of
each file is untouched. PATCH: editorial, no criteria-set change — the same
reading of rsr-criteria [versioning].rule-patch the 2.0.2 entry took.
Note `authority` already read 0-canon/constitution/ESTATE-CONSTITUTION.adoc
before this move while the `constitution` slot still read "constitution/". The
relocation resolves that inconsistency rather than creating one.
Gates
GATE A (check-canon-lockstep) 7 passed, 0 failed — all five artefacts
verified at their new paths and hashes
GATE D (check-standards-map) PASSED — 119/119 mapped, bidirectional
regression battery check-canonical-names, check-docs-presence,
check-implementation-inside-canon,
check-rsr-profile all identical to baseline
Sequence, per [canon.lockstep].order = spine-adopts-then-canon-releases: the
spine re-adopts these five hashes first, then this releases.
Contributor
|
Warning Review limit reachedNext included review available in 54 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (85)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
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.
Executes the 0-canon district of
standards-map.toml, which is the spec. The law stops living at the repository root.References rewritten in the same commit — a move with no reference rewrite is just a broken link.
standards-map.tomlfromvalues now record the migration as done.Why PATCH, not the "no bump" relocation the lock already documents
The lock's own 2026-09-17 entry took the escape route because the moved files were byte identical: "every sha256 below is UNCHANGED… The canon's identity is its hash set, and that is identical."
That escape is unavailable here — all five hashes changed, because the law names paths inside itself:
template-capability-gates.tomllists"constitution/"among the paths that define the canon;TEMPLATE-APPLICABILITY-POLICY.adocaspolicy;GOVERNANCE.adocas an alternative in thegovernance-tierrule.Those references were rewritten when the files moved, so the bytes are not identical, so the identity is not identical, so there is a new release identity for the spine to adopt. The obligation fires and the rule's own menu gives the category:
It also resolves a pre-existing inconsistency:
authorityalready read0-canon/constitution/ESTATE-CONSTITUTION.adocwhile theconstitutionslot still readconstitution/.Gates
Ordering
Per
[canon.lockstep].order = spine-adopts-then-canon-releases: the spine adopts first, then this releases. Merge the spine PR first.