Repository navigation
chore(sync): proof guide carries the checked-cone exception; anchor override names allowed languages - #39
Conversation
|
🟢 clean · commit 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.
Hypatia scan: 4 finding(s)
panic-attack assail: 18 finding(s)
pons asinorum: 9 finding(s)
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
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
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 88 finding(s)
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 finding(s)
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
accessibilitybot: 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. |
…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
255b907 to
3c66566
Compare
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3c66566b78
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| let lead = "\n- **Anchor override** (ANCHOR) — This repo's anchor " in | ||
| let tail = ". The anchor overrides the estate policy above." in | ||
| if has_allows && has_forbids then | ||
| "%{lead}allows, where the estate policy above denies: %{allows}; it forbids: %{forbids}%{tail}" |
There was a problem hiding this comment.
Stop repeating overridden languages as hard constraints
When an anchor allows an estate-denied language such as Go, this branch emits that Go is allowed, but the same generated pack still unconditionally says Never: banned langs (above) in .machine_readable/arrival-pack/arrival-pack.ncl:170 (and separately repeats AGPL). That leaves agents with mutually exclusive instructions in the exact scenario this change is intended to repair; the repo-specific constraints text must also account for anchor_allows_denied, rather than adding only the later override sentence.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Checked, and the finding is correct. The "Constraints here" line in arrival-pack.ncl (line 170) says "Never: banned langs (above), … AGPL" unconditionally. For an anchor that allows an estate-denied language, the pack would then say both "never" and "the anchor allows it".
It does not bite in this repo: bactrian's anchor allows no estate-denied language, so the generated CLAUDE.md carries no "allows" clause and the two lines agree.
Not fixed here, and this PR has merged: the line is the template's, carried unchanged, so the fix belongs in rsr-template-repo, and how the constraint should read when an anchor lifts a denial is the owner's wording to settle. Raised with the owner.
Generated by Claude Code
…GPL is never allowed (#464) ## Summary The generated "Constraints here" line in `CLAUDE.md` said "Never: banned langs (above)…" in every repo. Where a repo's anchor allows an estate-denied language, that contradicted the "Anchor override" line (Codex review of hyperpolymath/bactrian#39). Owner decisions by selector, 2026-11-19: approve the wording below; AGPL can never be allowed by an anchor. No repo's anchor allows a denied language today, so this is a latent fix. ## Changes - `.machine_readable/arrival-pack/arrival-pack.ncl` - Constraints line: unchanged when the anchor allows nothing denied. Otherwise: `Never: banned langs (above, except those this repo's anchor allows: Go), secrets, state files in repo root, AGPL.` It uses the same list as the override line, so the two cannot disagree. - AGPL is a licence, not a language: an anchor listing it under `:allowed` gets no "allows" wording for it. This changes the override line from #416 for that one case. - `tests/workflows/arrival_pack_anchor_override_test.sh` — five controls added (12 in all). - `.machine_readable/arrival-pack/README.adoc` — the anchor bullet says both things. `CLAUDE.md` is not in the diff: regenerating it gives the same bytes. ## RSR Quality Checklist ### Required - [ ] Tests pass (`just test`) — not run locally (the container lacks idris2 and zig). Left to CI. - [x] No banned language patterns - [x] No secrets, credentials, or `.env` files included ## Testing - `arrival_pack_anchor_override_test.sh` → 12 controls, 0 failed. - `just claude-md` then arrival-pack `verify.sh` → in sync; `CLAUDE.md` unchanged. - `governance_policy_test.sh` → exit 0. - The full `tests/` directory was not re-run. ## Follow-up, not in this PR The four minted repos (bactrian, atoma, sholes, ordinal-notation) carry the older engine. Their `CLAUDE.md` would not change, so a sync is not urgent. --- _Generated by [Claude Code](https://claude.ai/code/session_0136P7Zoc4g7WLgAwdMTnzPM)_ Co-authored-by: CLAUDE <355856132+HoTT-stuff@users.noreply.github.com> Co-authored-by: Claude Fable 5.2 <noreply@anthropic.com>



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, notASSUMED), 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.shgets a defaultcasebranch (SonarCloudshell:S131).tests/workflows/arrival_pack_anchor_override_test.sh— new, 7 controls, wired intoestate-rules.ymlas 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.adocbullet, because this repo's copy has older wording and I did not want to rewrite it by guess.RSR Quality Checklist
Required
just test) — not run locally. Left to CI..envfiles includedTesting
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.tests/directory was not re-run for this change.Generated by Claude Code