Skip to content

feat(receipt): record main run 44224818557, every leg in a pinned image (PWG-1) - #58

Open
hyperpolymath wants to merge 1 commit into
mainfrom
claude/record-main-run
Open

hyperpolymath wants to merge 1 commit into
mainfrom
claude/record-main-run

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

Summary

This records the first run on main after #57. Every leg in it ran in a digest-pinned image, so the pinned reader derives PWG-1 again for all six claims.

Closes #53. Its three steps are now all done:

CI run 44224818557 checked all three witnesses on 89302d2, the merge of #57:

  • Agda: debian:13-slim@sha256:a29215f6….
  • Rocq and Lean: ubuntu:24.04@sha256:73b99939….

Changes

  • Run ledger (scripts/grade-receipt.sh).
    • The run's three rows are now current. They are copied unchanged from its receipt job's output: 13 fields, each with its image, and the Agda row with its trusted-base binding.
    • The 7dfeab2 rows are marked superseded by this run. The ledger comment now describes them as history.
  • Receipt.
    • The :source-commit is now 89302d2 on main.
    • The old 7dfeab2 → 292d566 echo is no longer used by any current run, so the generator leaves it out.
    • The reader derives PWG-1 for N-1..N-3 and N-7..N-9. That matches the receipt the run's own job wrote.
  • Docs. README, PROOF-STATUS, the legs README, the proof-debt ledger and the CHANGELOG say PWG-1 again and name the run.

RSR Quality Checklist

Required

  • Tests pass. CI is green on 0ae0426. Locally, grade-receipt.sh --write and --check pass: the §8.5.3 git checks with the shared checker, the pinned reader at PWG-1, and the negative control.
  • No banned language patterns (bash 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 89302d2d1104930a5ce039e101775bc5d36f2dd6)
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-1  foundation-diverse false
  ...
PASS: negative control (the first claim recorded as :pwg PWG-2ii is refused: its legs support PWG-1)

🤖 Generated with Claude Code

https://claude.ai/code/session_01BYbQRtNu216R13jtZLmoqs

…ge (PWG-1)

CI run 44224818557 checked all three witnesses on 89302d2, the merge of
#57: the Agda leg in debian:13-slim@sha256:a29215f6..., the Rocq and Lean
legs in ubuntu:24.04@sha256:73b99939....  Its three rows, copied unchanged
from the run's receipt job, are now current; the 7dfeab2 rows are
superseded by it.

The receipt's :source-commit is 89302d2 on main, so the old 7dfeab2 ->
292d566 echo is no longer used and is left out.  The pinned reader
(standards 940a27a) derives PWG-1 for N-1..N-3 and N-7..N-9, as it did for
the receipt that run's own job wrote.  README, PROOF-STATUS, the legs
README, the proof-debt ledger and the CHANGELOG say PWG-1 again and name
the run.

Local: --write and --check pass (the shared git checks, the pinned reader
at PWG-1, the negative control).

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

coderabbitai Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The receipt and run ledger now record CI run 44224818557 on commit 89302d2. The documentation reports digest-pinned images and grade PWG-1 for claims N-1, N-2, N-3, N-7, N-8, and N-9.

Changes: Proof receipt refresh

Layer / File(s) Summary
Record current and superseded runs
scripts/grade-receipt.sh
The ledger adds current rows for run 44224818557 and marks the rows for run 43455458225 as superseded.
Update receipt evidence
verification/receipts/agda_praxis.deed
The receipt names commit 89302d2, updates six claims to PWG-1, records the current Agda, Rocq, and Lean runs, and retains earlier receipts as superseded.
Report updated proof status
CHANGELOG.adoc, PROOF-STATUS.adoc, README.adoc, docs/proof-debt.adoc, verification/legs/README.adoc
These documents report run 44224818557, commit 89302d2, digest-pinned images, and PWG-1 for the six claims.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related issues

Possibly related PRs

Merge Risk: Minimal · up to 0ae04

This change updates the proof receipt and documentation to record CI run 44224818557 on commit 89302d2 and to report PWG-1 for six claims. No concrete problems were found, so it looks ready to merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: recording CI run 44224818557 on main as the receipt evidence, with every leg in a pinned image, and the resulting PWG-1 grade. It matches the objectives and the change…
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.
Description check Passed The description follows the repository template. It has a Summary that states the purpose and links the run, a Changes list covering the ledger, receipt, and docs, and a checklist with most items tick…
Full details: Title check

Explanation

The title names the main change: recording CI run 44224818557 on main as the receipt evidence, with every leg in a pinned image, and the resulting PWG-1 grade. It matches the objectives and the changeset. The title uses a conventional commit prefix and is 79 characters, which is slightly long but readable.

Full details: Description check

Explanation

The description follows the repository template. It has a Summary that states the purpose and links the run, a Changes list covering the ledger, receipt, and docs, and a checklist with most items ticked. It also gives a Testing section with the command outputs. The description says it closes #53. Three points are weaker: the Screenshots section is absent (it is optional, marked 'if applicable'), the 'Tests pass' item is ticked based on local runs plus a CI green claim on 0ae0426, and the CHANGELOG and documentation items are ticked. The description does not mention the ROADMAP, TOPOLOGY, or deed status/maturity items, which are conditional and may not apply. Overall the description is mostly complete and specific.

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

Commits

Reviewing files that changed from the base of the PR and between 89302d2 and 0ae0426.

Files selected for processing: 7

  • CHANGELOG.adoc
  • PROOF-STATUS.adoc
  • README.adoc
  • docs/proof-debt.adoc
  • scripts/grade-receipt.sh
  • verification/legs/README.adoc
  • verification/receipts/agda_praxis.deed

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

@sonarqubecloud

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 0ae042609272 · run 44227050956 · scope: this change (7 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:162 — 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:33 — 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:110 — 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.

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 18, 2026 02:58
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.

PWG-1 rests on non-container Rocq/Lean legs: pin every proof job to a digest-pinned image

3 participants