Skip to content

chore(canon): re-pin [canon] to standards canon.lock 2.1.5 - #20

Merged
hyperpolymath merged 1 commit into
mainfrom
marina/canon-pin-2.1.5
Nov 14, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
marina/canon-pin-2.1.5

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

.machine_readable/rsr-profile.a2ml declares canon 2.1.1, but hyperpolymath/standards canon.lock is at 2.1.5. The Canon lockstep job in dogfood-gate.yml compares 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.5
    • gates_sha256: e70efd2f… → 5c510bba025be718deebb12d0333bfe7db2da43c66578b728b1a334df65290b1
    • criteria_sha256: unchanged (6a5aa885…), which matches canon.lock
    • One dated line added to the adoption history comments, in the file's existing style.
  • declares-against = "2.1.1-draft" and PROVENANCE.a2ml are 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 pin logic from dogfood-gate.yml (the same canon_key and artefact_hash readers) locally against canon.lock on standards main, the URL the workflow fetches:

OK  version 2.1.5
OK  criteria_sha256 6a5aa8857bd0d0d58ef48827938ca17c251b6b854dacf59d306388d61694d82a
OK  gates_sha256 5c510bba025be718deebb12d0333bfe7db2da43c66578b728b1a334df65290b1

The Canon lockstep check 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

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
@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Chores
    • Updated the recorded canon version to 2.1.5; the criteria hash remains unchanged.

The canon pin changes from version 2.1.1 to 2.1.5. The gates hash and dated adoption comment also change. The criteria hash and lockstep date remain unchanged.

Changes: Canon pin update

Layer / File(s) Summary
Update canon pin
.machine_readable/rsr-profile.a2ml
The canon version and gates hash change. A dated comment records the adoption. The criteria hash and lockstep date remain unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: Minimal · up to 4cb4c

This updates the declared canon pin to version 2.1.5 with a new gates hash. It does not change runtime behavior. The PR's Canon lockstep check will confirm the values match upstream.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: re-pinning the [canon] declaration to standards canon.lock 2.1.5. The diff updates the version and gates_sha256 in .machine_readable/rsr-profile.a2ml, which matches th…
Description check Passed The description follows the template's Summary and Changes sections with specific detail. It explains why the pin changed and lists each field change. It also includes a Testing section with local ver…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the main change: re-pinning the [canon] declaration to standards canon.lock 2.1.5. The diff updates the version and gates_sha256 in .machine_readable/rsr-profile.a2ml, which matches the title. The title uses a conventional commit prefix and is specific.

Full details: Description check

Explanation

The description follows the template's Summary and Changes sections with specific detail. It explains why the pin changed and lists each field change. It also includes a Testing section with local verification output. The template's RSR Quality Checklist is not present, and the Screenshots section is omitted, but the checklist items are mostly not applicable to a single-file metadata pin. The required checklist is missing, so the author should confirm the Required items or mark them not applicable.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 25cd4b6b-3c0e-46d8-9dde-29b4293ae811
Commits

Reviewing files that changed from the base of the PR and between 109b00c and 4cb4c88.

Files selected for processing: 1

  • .machine_readable/rsr-profile.a2ml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 31

  • GitHub Check: CodeRabbit
  • GitHub Check: 🟡 CHECK: Groove manifest check
  • GitHub Check: Dogfooding compliance summary
  • GitHub Check: Patch Bridge CVE triage
  • GitHub Check: panic-attack assail
  • GitHub Check: Canon lockstep
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Validate DEED manifests
  • GitHub Check: 🔴 GATE: Empty-linter (invisible characters)
  • GitHub Check: RSR oracle — dogfood this repo
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: estate-rules
  • GitHub Check: lint
  • GitHub Check: openssf-compliance
  • GitHub Check: 🟡 CHECK: Validate eclexiaiser manifest
  • GitHub Check: 🟡 CHECK: Validate K9 contracts
  • GitHub Check: Test (Test + Aqua) (1.10, ubuntu-latest)
  • GitHub Check: 🟡 CHECK: Groove manifest check
  • GitHub Check: analyze (actions, none)
  • GitHub Check: Test (Test + Aqua) (1, ubuntu-latest)
  • GitHub Check: check
  • GitHub Check: Format (JuliaFormatter)
  • GitHub Check: docs
  • GitHub Check: check
  • GitHub Check: Static analysis (JET)
  • GitHub Check: actions.lock is in sync with the workflow YAML
  • GitHub Check: Validate DEED manifests
  • GitHub Check: Runtime Policy
  • GitHub Check: 🔴 GATE: Empty-linter (invisible characters)
  • GitHub Check: SonarQube
Additional context used

Code guidelines: 3

.windsurfrules — auto-discovered
.github/copilot-instructions.md — auto-discovered
.cursorrules — auto-discovered
Path-based instructions: 2

Source excerpt:

CodeRabbit inference engine (.windsurfrules)

Files:

  • .machine_readable/rsr-profile.a2ml
Source excerpt: State files (.a2ml) live in `.machine_readable/` ONLY, never the root.

CodeRabbit inference engine (.github/copilot-instructions.md)

Files:

  • .machine_readable/rsr-profile.a2ml

@sonarqubecloud

Copy link
Copy Markdown

@linear-code
linear-code Bot marked this pull request as ready for review November 14, 2026 19:13

Copy link
Copy Markdown
Owner Author

The failing estate-rules check is not caused by this PR. It fails at tests/shape/repo_map_determinism_test.sh: FAIL: committed REPOSITORY-MAP.adoc is stale — run: just repo-map. I ran the same test on a clean checkout of main (109b00c), and it fails there in the same way. This PR changes only values inside .machine_readable/rsr-profile.a2ml. It adds no file and removes none, so it does not change what the map lists. The stale map needs a separate just repo-map regeneration on main.


Generated by Claude Code

@hyperpolymath
hyperpolymath merged commit bd51089 into main Nov 14, 2026
37 of 38 checks passed
@hyperpolymath
hyperpolymath deleted the marina/canon-pin-2.1.5 branch November 14, 2026 19:26
hyperpolymath added a commit that referenced this pull request Nov 14, 2026
## 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>
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.

3 participants