Skip to content

chore(canon): re-adopt canon 2.0.2 - #109

Merged
hyperpolymath merged 1 commit into
mainfrom
chore/re-adopt-canon-2.0.2
Sep 17, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
chore/re-adopt-canon-2.0.2

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Sep 17, 2026 •

Copy link
Copy Markdown
Owner

The canon's 2.0.2 release corrects the machine tree's spelling in its two normative artefacts: machine-readable/ → .machine_readable/. Ruling R-A settled the spelling; the law had been naming the minority form.

Re-pinned here, all three values:

pin was now
version 2.0.1 2.0.2
criteria_sha256 efd024ad… 7804d77127001ed50263f0783d8a11f7211e72cb5e9f6443f2acde4b08d9ab1e
gates_sha256 8b1a77669c9a… 6a8b9b420519dccdd2c586da06a9a302bdbbb3dc917f49e4a7b308882471d68a

⚠️ This PR is RED until the canon releases, and that is the rule working

[canon].order is spine-adopts-then-canon-releases, and the Canon lockstep job compares all six values — the F8 fix. Canon main still says 2.0.1, so this cannot be green on its own. It lands with hyperpolymath/standards#818, seconds apart, exactly as the Phase 1 pair did.

F8 is why this is safe to attempt: before it, gates_sha256 was recorded and never compared, so a half-done re-pin would have been invisible. Six values, two directions, empty reads refused.

Witness

Run against the canon tree at the 2.0.2 release, the spine's own extractors print MATCH for all three pins.

The canon's 2.0.2 release corrects the machine tree's spelling in its two
normative artefacts: `machine-readable/` → `.machine_readable/`. Ruling R-A
settled the spelling; the law had been naming the minority form.

Re-pinned, all three values:

    version          2.0.1  -> 2.0.2
    criteria_sha256  efd024ad… -> 7804d77127001ed50263f0783d8a11f7211e72cb5e9f6443f2acde4b08d9ab1e
    gates_sha256     8b1a77669c9a… -> 6a8b9b420519dccdd2c586da06a9a302bdbbb3dc917f49e4a7b308882471d68a

ORDER MATTERS, AND THIS HALF GOES FIRST

[canon].order is spine-adopts-then-canon-releases: the canon cannot land 2.0.2
while pinning hashes this repo has not adopted. Gate A fails the canon until
this is in.

So **this change is red until the canon releases** — the `Canon lockstep` job
compares all six values (the F8 fix) and canon main still says 2.0.1. The two
land together, as the Phase 1 pair did. That is the ordering rule working, not a
broken gate.

F8 is why this is safe to attempt at all: before it, `gates_sha256` was recorded
and never compared, so a half-done re-pin would have been invisible. Six values,
two directions, empty reads refused.

Witness: the spine's own extractors, run against the canon tree at the 2.0.2
release, print MATCH for all three pins.
@hyperpolymath
hyperpolymath merged commit aec8a70 into main Sep 17, 2026
42 of 48 checks passed
@coderabbitai

coderabbitai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Next included review available in 17 minutes.

Check out review usage here.

View limit details

Limit 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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 765a5a16-477d-45e9-bb04-5d168369af6a

📥 Commits

Reviewing files that changed from the base of the PR and between 7cb285f and c3409a1.

📒 Files selected for processing (1)
  • .machine_readable/rsr-profile.a2ml

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hyperpolymath
hyperpolymath deleted the chore/re-adopt-canon-2.0.2 branch September 17, 2026 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant