Skip to content

chore(sync): proof guide carries the checked-cone exception; anchor override names allowed languages - #22

Merged
hyperpolymath merged 2 commits into
mainfrom
claude/proof-guide-and-anchor-override
Nov 15, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
claude/proof-guide-and-anchor-override

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Summary

Carries hyperpolymath/rsr-template-repo#416 here, at template 3396f1f. Owner decision by selector, 2026-11-15 ("Fix template and the four repos").

Changes

  • verification/proofs/README.adoc — gains the PROOF-POLICY §1.1 exception (a whole import cone that passes safe mode with zero postulates is checked, not ASSUMED), so the guide and the generated Proofs block agree. governance_policy_test.sh (the template's) asserts it in both.
  • .machine_readable/arrival-pack/arrival-pack.ncl — also names any language the anchor allows that the estate policy denies. extract.sh gets a default case branch (SonarCloud shell:S131).
  • tests/workflows/arrival_pack_anchor_override_test.sh — new, 7 controls, wired into estate-rules.yml as one step after the Nickel typecheck step. No action pins change.
  • CLAUDE.md — regenerated. The Anchor override line is unchanged here (this anchor allows no estate-denied language). The only new text is the template's chora/CLADE note (docs(arrival-pack): the chora and CLADE are different things rsr-template-repo#415), which the same engine file carries.

Each carried file was byte-identical to the template's pre-#416 version, so they are taken verbatim. Not carried: the arrival-pack README.adoc bullet, because this repo's copy has older wording and I did not want to rewrite it by guess.

Known and not fixed here: estate-rules was red on main when #19 merged, because docs/status/PROOF-STATUS.adoc has no rows in a == Claims table. If that is still so, this PR's estate-rules run stops at the same step.

RSR Quality Checklist

Required

  • Tests pass (just test) — not run locally. Left to CI.
  • No banned language patterns
  • No secrets, credentials, or .env files included

Testing

  • arrival-pack verify.sh → in sync with the deed.
  • arrival_pack_anchor_override_test.sh → 7 controls, 0 failed.
  • governance_policy_test.sh, workflow_edges_test.sh, check_lock_sync_test.sh → exit 0.
  • check-lock-sync.sh, check-workflow-edges.sh, check-mint-tokens.sh, check-no-placeholders.sh, just validate-repo-map → pass.
  • The full tests/ directory was not re-run for this change.

Generated by Claude Code

Summary by CodeRabbit

  • New Features
    • Arrival packs now flag anchor languages that conflict with estate language restrictions, including when the anchor also forbids languages.
    • Generated packs clarify the distinction between identity information and repository content ordering.
  • Documentation
    • Clarified how legacy CLADE files contribute to identity and state information.
    • Documented when proof dependencies are verified versus recorded as assumed.
  • Tests
    • Added coverage for arrival-pack language overrides and proof dependency policies.

@github-actions

github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit cf84f8ea7d6f · run 43711345900 · scope: this change (7 file(s))

Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change.

Unique graded findings across gating and advisory rows: 20 (20 reporter observations; 19 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Raw Hypatia alert-derived observations: 36 (code-scanning, Dependabot and secret-scanning; some may also be in SARIF; not an extra total).

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panic-attack assail advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
pons asinorum advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
echidnabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panicbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
sustainabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
glambot (presentation quality) advisory 🔵 minor 0 0 0 6 — same commit (no revision comparison)
seambot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
finishingbot (release readiness) advisory 🔴 high 0 9 5 0 — same commit (no revision comparison)
cipherbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
Hypatia scan: 4 finding(s)
  • 4 further finding(s) in files this change does not touch: reported, not graded (0 critical, 3 high).
panic-attack assail: 20 finding(s)
  • 20 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
pons asinorum: 9 finding(s)
  • 9 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
  • ⚪ not applicable: template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
  • 11 further finding(s) in files this change does not touch: reported, not graded (0 critical, 10 high).
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
  • ⚪ not applicable: panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
  • ⚪ not applicable: reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 94 finding(s)
  • info GS-001 — Install git-seo for comprehensive SEO analysis: https://github.com/hyperpolymath/git-seo
  • info MACH-007 — ECOSYSTEM.scm not found in .machine_readable/ directory.
  • info MACH-007 — META.scm not found in .machine_readable/ directory.
  • info MACH-007 — STATE.scm not found in .machine_readable/ directory.
  • info MACH-005 — No robots.txt found. Consider adding one for crawler control.
  • info VIS-005 — CLAUDE.md:9 — Line 177 characters exceeds max length of 80.
  • 88 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
  • ⚪ not applicable: template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 185 finding(s)
  • high V1-DOC-ROADMAP.adoc — Required file ROADMAP.adoc not found (Project roadmap).
  • high TOOL-001 — .tool-versions file not found for asdf/mise version management.
  • high SCM-001-NEUROSYM.scm — Required SCM file NEUROSYM.scm not found (Neurosymbolic AI documentation).
  • high SCM-001-AGENTIC.scm — Required SCM file AGENTIC.scm not found (Agentic AI integration documentation).
  • high SCM-001-PLAYBOOK.scm — Required SCM file PLAYBOOK.scm not found (Operational playbooks and procedures).
  • high SCM-001-ECOSYSTEM.scm — Required SCM file ECOSYSTEM.scm not found (Project's place in the ecosystem).
  • high SCM-001-META.scm — Required SCM file META.scm not found (Meta-level information and architectural decisions).
  • high SCM-001-STATE.scm — Required SCM file STATE.scm not found (Project state and progress tracking).
  • high PH-100 — Found 128 placeholders, exceeds maximum allowed (0)
  • medium V1-COM-CONTRIBUTING.md — CONTRIBUTING.md file not found (Contribution guidelines).
  • medium V1-COM-CODE_OF_CONDUCT.md — CODE_OF_CONDUCT.md file not found (Code of conduct).
  • medium V1-SEC-001 — SECURITY.md not found for responsible disclosure.
  • medium TEST-001 — Could not determine if this is a Rust or Deno project.
  • medium REL-004 — No SECURITY.md file found
  • 171 further finding(s) in files this change does not touch: reported, not graded (0 critical, 4 high).
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
  • ⚪ not applicable: template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
  • ⚪ not applicable: template default: enrol once the repository serves HTML

Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run.

Copy link
Copy Markdown
Owner Author

estate-rules is red on this PR, and the failure is not from this change. It is the same one as on #19.

  • Failing step: tests/workflows/proof_claims_rows_test.sh — "docs/status/PROOF-STATUS.adoc has no rows in a == Claims table".
  • Not touched here: this PR does not change PROOF-STATUS.adoc or that test.
  • Red on the base too: estate-rules fails on main at 26066d4 (this PR's base) and at 8533fcf before it.

No fix is pushed here: the cure is a Claims table in atoma's own proof status file, which is proof-status content and outside this sync. The job stops at that step, which comes before the new "Arrival pack renders both sides of an anchor override" step, so that step has not run in CI here. It passes locally (7 controls, 0 failed).


Generated by Claude Code

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 15, 2026 11:24
@hyperpolymath
hyperpolymath enabled auto-merge (squash) November 15, 2026 11:24
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-15T12:09:59.622163Z 45eea0c New commits
🔒 Security Review ✅ Completed 2026-11-15T12:12:09.521277Z 45eea0c New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Repository owner deleted a comment from coderabbitai Bot Nov 15, 2026
@hyperpolymath
hyperpolymath force-pushed the claude/proof-guide-and-anchor-override branch from ce6dd58 to b0fe27a Compare November 15, 2026 11:44
Repository owner deleted a comment from coderabbitai Bot Nov 15, 2026
Repository owner deleted a comment from coderabbitai Bot Nov 15, 2026
@hyperpolymath
hyperpolymath enabled auto-merge (squash) November 15, 2026 11:50
…verride names allowed languages (rsr-template-repo#416)

Carries rsr-template-repo#416 here, at template 3396f1f:

- verification/proofs/README.adoc gains the PROOF-POLICY §1.1 exception (a
  whole import cone that passes safe mode with zero postulates is checked, not
  ASSUMED), so the guide and the generated Proofs block agree.
  governance_policy_test.sh asserts it in both.
- arrival-pack.ncl also names any language the anchor allows that the estate
  policy denies; extract.sh gets a default case (SonarCloud shell:S131).
  New controls: tests/workflows/arrival_pack_anchor_override_test.sh, wired
  into estate-rules.yml as one step.
- CLAUDE.md regenerated. The Anchor override line is unchanged here; the only
  new text is the template's chora/CLADE note (rsr-template-repo#415), which
  the same engine file carries.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zoc4g7WLgAwdMTnzPM
@hyperpolymath
hyperpolymath force-pushed the claude/proof-guide-and-anchor-override branch from b0fe27a to cf84f8e Compare November 15, 2026 11:53
Repository owner deleted a comment from coderabbitai Bot Nov 15, 2026
@hyperpolymath
hyperpolymath merged commit 3843e26 into main Nov 15, 2026
44 checks passed
@coderabbitai

coderabbitai Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 41 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between b0fe27a and 45eea0c.

Files selected for processing: 7

  • .github/workflows/estate-rules.yml
  • .machine_readable/arrival-pack/arrival-pack.ncl
  • .machine_readable/arrival-pack/extract.sh
  • CLAUDE.md
  • tests/workflows/arrival_pack_anchor_override_test.sh
  • tests/workflows/governance_policy_test.sh
  • verification/proofs/README.adoc

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

@hyperpolymath
hyperpolymath deleted the claude/proof-guide-and-anchor-override branch November 15, 2026 12:07
@sonarqubecloud

Copy link
Copy Markdown

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