Skip to content

fix(receipt): record checker images (PROOF-POLICY §8.2); legs in a pinned image - #57

Merged
hyperpolymath merged 2 commits into
mainfrom
claude/receipt-images
Nov 18, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
claude/receipt-images

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

PROOF-POLICY §8.2 now counts a witness toward PWG-1 only when its current receipt records the digest-pinned image its checker ran in. This comes from the owner ruling of 2026-11-16, landed as metadatastician/standards#1625.

#54 pinned the receipt tools at standards f6ebc5e, which predates that rule. This PR moves the pin to 940a27a, standards main, and does three things:

  • records what the last run can show;
  • states the grade the current reader derives;
  • runs the legs in a pinned image, so the next recorded run restores PWG-1.

Until that run is recorded, the committed receipt reads PWG-2ii. The Rocq and Lean legs of run 43455458225 ran on the bare ubuntu-24.04 runner. That runner has no digest, so under the current rule those witnesses cannot count toward PWG-1.

Evidence from this PR's CI

Run 44214592597, on 1c28ec9, ran all three legs in pinned images:

  • Agda: debian:13-slim@sha256:a29215f6….
  • Rocq and Lean: ubuntu:24.04@sha256:73b99939….
  • Rows: each row this run prints has the image as its 13th field.
  • Grade: the receipt of this run derives PWG-1 for N-1..N-3 and N-7..N-9.
  • Committed receipt: passes --check at PWG-2ii.

Changes

  • Pins. All four receipt tools are pinned at standards 940a27a, each by sha256.
  • Agda row. It records debian:13-slim@sha256:a29215f6…, the container proofs.yml pinned for the Agda job at the run's own commit 7dfeab2.
  • proofs.yml.
    • The legs job runs in ubuntu:24.04@sha256:73b99939…, the image lintel#31 uses. It installs its tools as root and marks the workspace safe for git, as the Agda job does.
    • Both jobs pass --image to --run-row. The value is read from the job's own container: line at the commit under test, so there is one source of truth.
    • Both jobs also pass --axioms none, which the generator at 940a27a requires. The gates refuse any axiom.
  • Docs. README, PROOF-STATUS, the legs README, the proof-debt ledger and the CHANGELOG now say PWG-2ii, and why.

After merge

Record the first run on main, using the rows its receipt job prints. All three legs then carry an image, and the reader derives PWG-1 again.

RSR Quality Checklist

Required

  • Tests pass. CI is green on 1c28ec9, including the Agda, legs and proof-receipt jobs. Locally, --write and --check pass.
  • No banned language patterns (bash, YAML and AsciiDoc only).
  • No banned functions.
  • SPDX headers unchanged.
  • No secrets.

As Applicable

  • Documentation updated.
  • CHANGELOG updated.

Testing

PASS: verification/receipts/agda_praxis.deed matches the tree and the ledgers (source-commit 292d566a81a9bafcd6bdf7f3caab7fc2ebad36bd)
PASS: git checks of §8.5.3 (shared checker, standards 940a27af1e25, --branch refs/remotes/origin/main)
PASS: the pinned reader (standards 940a27af1e25) accepts verification/receipts/agda_praxis.deed
  N-1  PWG-2ii  foundation-diverse false
  ...
PASS: negative control (the first claim recorded as :pwg PWG-1 is refused: its legs support PWG-2ii)

🤖 Generated with Claude Code

https://claude.ai/code/session_01BYbQRtNu216R13jtZLmoqs

…nned image

PROOF-POLICY §8.2 (owner ruling 2026-11-16, standards #1625) counts a
witness toward PWG-1 only when its current receipt records the
digest-pinned image its checker ran in.  The receipt tools are now pinned
at standards 940a27a, whose reader enforces that.

- The current Agda row records debian:13-slim@sha256:a29215f6..., the
  container proofs.yml pinned for the Agda job at the run's own commit
  7dfeab2.  The Rocq and Lean legs of that run ran on the bare
  ubuntu-24.04 runner, which has no digest, so their rows carry none and
  every claim now reads PWG-2ii.  README, PROOF-STATUS, the legs README
  and the proof-debt ledger say so and why.
- The legs job runs in ubuntu:24.04@sha256:73b99939..., installing its
  tools as root.  Both jobs pass --image, read from their own container:
  line at the commit under test, and --axioms none (the gates refuse any
  axiom), which the generator at 940a27a requires.  The first run recorded
  on main will carry an image for all three legs and restore PWG-1.

Local: --write and --check pass (the shared git checks, the pinned reader
at PWG-2ii for N-1..N-3 and N-7..N-9, the negative control); --run-row
with --axioms and --image writes a 13-field row for each leg.  Not run
here: the provers in their images; CI runs them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BYbQRtNu216R13jtZLmoqs
@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 1c28ec9caad1 · run 44215801187 · scope: this change (8 file(s))

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

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — no comparable baseline
panic-attack assail advisory 🟢 clean 0 0 0 0 — no comparable baseline
pons asinorum advisory 🟢 clean 0 0 0 0 — no comparable baseline
finishingbot (release readiness) advisory 🔴 high 0 9 9 2 — no comparable baseline
glambot (presentation quality) advisory 🔵 minor 0 0 0 10 — no comparable baseline
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — no comparable baseline
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
cipherbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
echidnabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
panicbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
seambot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
sustainabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline
Hypatia scan: 20 finding(s)
  • 20 further finding(s) in files this change does not touch: reported, not graded (0 critical, 4 high).
panic-attack assail: 16 finding(s)
  • 16 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
pons asinorum: 9 finding(s)
  • 9 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
finishingbot (release readiness): 174 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 124 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
  • medium CLM-006 — verification/legs/README.adoc — Documentation references non-existent file: lean/Axioms.lean
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: e2e.yml.template
  • medium CLM-006 — CHANGELOG.adoc — Documentation references non-existent file: hypatia-scan.yml
  • medium PH-001 — CHANGELOG.adoc:154 — Found 'TODO' in: `FROM …:latest` lines and a body of TODO comments built nothing and failed
  • info CLM-003 — README.adoc — README missing 'Usage examples' section
  • info CLM-003 — README.adoc — README missing 'Installation instructions' section
  • 154 further finding(s) in files this change does not touch: reported, not graded (0 critical, 3 high).
glambot (presentation quality): 95 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 — PROOF-STATUS.adoc:40 — Line 85 characters exceeds max length of 80.
  • info VIS-005 — README.adoc:8 — Line 209 characters exceeds max length of 80.
  • info VIS-005 — verification/legs/README.adoc:76 — Line 84 characters exceeds max length of 80.
  • info VIS-005 — docs/proof-debt.adoc:7 — Line 83 characters exceeds max length of 80.
  • info VIS-005 — CHANGELOG.adoc:102 — Line 84 characters exceeds max length of 80.
  • 85 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
rhodibot (RSR compliance): 13 finding(s)
  • 13 further finding(s) in files this change does not touch: reported, not graded (0 critical, 12 high).
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
  • ⚪ not applicable: template default: enrol once the repository serves HTML
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
  • ⚪ not applicable: template default: enrol once the repository implements cryptography
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
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
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
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)

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.

In the pinned ubuntu image, actions/checkout marks the workspace as a safe
directory only under a temporary HOME, so the next git call refused the
clone ("dubious ownership"; run 44214405363), as it did in the Agda job's
container before.  The legs job now marks it for the job, as the Agda job
does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BYbQRtNu216R13jtZLmoqs
@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 18, 2026 01:26
Repository owner deleted a comment from coderabbitai Bot Nov 18, 2026
@hyperpolymath
hyperpolymath merged commit 89302d2 into main Nov 18, 2026
75 checks passed
@hyperpolymath
hyperpolymath deleted the claude/receipt-images branch November 18, 2026 02:39
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