Repository navigation
chore(canon): re-pin [canon] to standards canon.lock 2.1.5 - #20
Conversation
rsr-profile.a2ml declared canon 2.1.1 with gates_sha256 e70efd2f..., while standards canon.lock is 2.1.5 with gates 5c510bba.... criteria_sha256 is unchanged. The [canon] version and gates hash now match canon.lock, with a dated line in the adoption history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZmtZYw7MBqRg41GWTw
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
|
|
The failing Generated by Claude Code |
## Summary `estate-rules` fails on `main` at `tests/shape/repo_map_determinism_test.sh`, because the committed `docs/architecture/REPOSITORY-MAP.adoc` is stale. #20 hit the same failure. This PR commits the output of `just repo-map` run on `main` (`bd51089`). ## Changes - `docs/architecture/REPOSITORY-MAP.adoc`: one row added, for `ext/` (optional): "Julia package extensions: Julia loads an [extensions] entry from ext/ at the package root, so it cannot move; present only where Project.toml declares one". The map was most likely not regenerated when the `AcceleratorGateExt` extension came in with #12. The file was generated, not edited by hand. ## Testing ``` before: FAIL: committed REPOSITORY-MAP.adoc is stale (run: just repo-map) just repo-map: wrote docs/architecture/REPOSITORY-MAP.adoc after: PASS: repository map is byte-identical across locales, and committed copy is current ``` Diff: 4 lines added. The commit is SSH-signed. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7ZmtZYw7MBqRg41GWTw)_ Co-authored-by: Claude <noreply@anthropic.com>



Summary
.machine_readable/rsr-profile.a2mldeclares canon2.1.1, buthyperpolymath/standardscanon.lockis at2.1.5. TheCanon lockstepjob indogfood-gate.ymlcompares these values. This PR re-pins[canon]to the released identity, as was done today in EpistemicTypes.jl, Protoctist.jl and ResidualEvidenceTypes.jl.Changes
.machine_readable/rsr-profile.a2ml[canon]:version:2.1.1→2.1.5gates_sha256:e70efd2f…→5c510bba025be718deebb12d0333bfe7db2da43c66578b728b1a334df65290b1criteria_sha256: unchanged (6a5aa885…), which matches canon.lockdeclares-against = "2.1.1-draft"andPROVENANCE.a2mlare not changed. Canon lockstep does not compare the first, and the second is the mint record.No test in this repo hard-codes the canon tuple.
Testing
I ran the
Compare this repo's declared pinlogic fromdogfood-gate.yml(the samecanon_keyandartefact_hashreaders) locally againstcanon.lockon standardsmain, the URL the workflow fetches:The
Canon lockstepcheck on this PR is the real test. This pin records which canon the repo tracks. Whether the repo meets the 2.1.5 gates is assessed by the separate RSR checks. This PR does not claim that it does.The commit is SSH-signed.
Generated by Claude Code