Skip to content

docs: bring PROOF-STATUS.adoc to the template form and record the ASSUMED bridge (replaces #23) - #27

Merged
hyperpolymath merged 2 commits into
mainfrom
fix/proof-status-trust-boundary
Nov 14, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
fix/proof-status-trust-boundary

Conversation

@hyperpolymath

@hyperpolymath hyperpolymath commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Replaces #23.

Self-reviewed against what Codex and CodeRabbit raised on #23 and its sibling Apodeixis.jl#31:

  • just proof-status printing no status (Codex): a template recipe issue. The source fix is rsr-template-repo#385, which this repository gets at the next template sync. Not patched here.
  • n/a versus ungraded for the six engineering rows (CodeRabbit, minor): not changed. The owner ruled that every open row is ungraded with no PWG asserted. The template's vocabulary said engineering proofs are n/a, which contradicted its own no-receipt sentence; that is fixed at source in rsr-template-repo#392. (An earlier version of this note wrongly said the template's intro paragraph already said ungraded: that sentence is in this repository's file, not the template.)

Checked locally: check-hypatia-rule-order.sh exits 0, asciidoctor 2.0.26 renders the file clean, and the template's proof-claims-rows.sh (from #385) prints all 7 rows. Three checks fail the same way on #23's base, so this PR does not cause them: check-no-placeholders.sh (8 files with unfilled tokens), check-mint-tokens.sh and check-hypatia-ignore.sh (stale build/docs-seed/ exemption). Those are cleared by #24 and #26. The DEED line 228 and root-shape reds on main are unchanged. Not proven here: a CI run.


Generated by Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated proof-status reporting to show each claim’s status, verification grade, recheck results, and receipt. Clarified how grades and verification legs are assessed, documented a trust-boundary assumption, and listed verification commands.
    • Clarified the witness-entry requirements, including that required clauses must be present in a single deed and cannot be inferred from fields within those clauses.

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Caution

Review failed

The pull request is closed.

Walkthrough

The changes clarify witness-map comments and replace proof-progress totals with a claim table. The proof-status document also defines status terms, records a trust boundary, and updates verification commands.

Changes: Proof Status and Witness Model

Layer / File(s) Summary
Witness gate and probe comments
.machine_readable/coaptation/witness-map.ncl
The comments describe the Must/Trust gate model, state that each descriptile entry needs a defensible witness, and specify the clauses required by the directory probe.
Proof-status policy and claim record
docs/status/PROOF-STATUS.adoc
The document defines claim statuses, Proof Witness Grades, recheck legs, and receipt requirements. It lists seven open, ungraded claims, records the Idris2-to-Nickel correspondence as an assumed boundary, and updates the verification commands.

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

Change: Other

Merge Risk: Low · up to a3714

This PR only edits documentation and comments. Two inconsistencies should be fixed: the witness-map comment overstates when an empty witness list is refuted, and the proof-status grading vocabulary conflicts with the open Idris2 rows. Neither affects runtime behavior, so the risk of merging is low.

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 marked this pull request as ready for review November 14, 2026 17:14
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 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-14T17:29:34.746129Z 450003b New commits
🔒 Security Review ✅ Completed 2026-11-14T17:27:37.789459Z 450003b 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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cdfe1c94ee

ℹ️ 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".

| ID | Proof | Blocked By | Notes

| — | — | — | —
| ID | Claim (and the artefact that proves or tests it) | Token | PWG | Rocq leg | Lean leg | Receipt

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update proof-status for the new claims table

When users run just proof-status, the existing recipe in build/just/proofs.just only searches for the removed | **Total** summary row, so this new table makes the command report (No summary row in docs/status/PROOF-STATUS.adoc) instead of summarizing the seven open obligations. Update that recipe to parse the claims rows as part of this format change, or retain a compatible summary row.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified: build/just/proofs.just line 57 on main greps only for the removed Total summary row, so just proof-status would print '(No summary row ...)' for the Claims table. That recipe is template-owned and identical to the template's pre-fix version, so the fix belongs at the source: rsr-template-repo#385 (scripts/proof-claims-rows.sh and the proofs.just branch, 12 guard controls, open and not yet merged). This PR does not edit the recipe, to avoid diverging from the template; bactrian picks the fix up with the template catch-up that is on hold. Left unresolved on purpose until that lands. Nothing here claims proof-status works for the new table yet.


Generated by Claude Code

…m, with the seven obligations as open rows

Replaces #17. The template-form PROOF-STATUS.adoc, with the {{PROJECT}} title
token filled (bactrian), and the seven mandatory obligations from
PROOF-NEEDS.adoc (ABI-1..5, TP-1, TP-2) restated as rows with status token open,
PWG ungraded and no receipt, so the census sees open obligations. No row claims a
proof. Row text is copied from PROOF-NEEDS.adoc. witness-map.ncl is unchanged
from #17.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
…boundary

The trust boundary said none, but the coaptation README and Coaptation.idr
declare the Idris2-model-to-coapt.ncl correspondence ASSUMED (argued, not
kernel-checked). List it, and say that no Claims row rests on it.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
@hyperpolymath
hyperpolymath force-pushed the fix/proof-status-trust-boundary branch from a3714ba to 450003b Compare November 14, 2026 17:25
@hyperpolymath
hyperpolymath merged commit 816b268 into main Nov 14, 2026
1 check passed
@hyperpolymath
hyperpolymath deleted the fix/proof-status-trust-boundary branch November 14, 2026 17:25
@sonarqubecloud

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 450003b28a

ℹ️ 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".

| ABI-5 | C ABI compliance (`CABICompliant`, `FieldsAligned`) (artefact: `verification/proofs/idris2/ABI/Compliance.idr`) | open | ungraded | — | — | —
| TP-1 | Core data type well-formedness (artefact: `verification/proofs/idris2/Types.idr`) | open | ungraded | — | — | —
| TP-2 | Public API type safety (exported functions). PROOF-POLICY §1 assigns APIs to Idris2; the Lean file is the shipped example until a project ports it (artefact: `verification/proofs/lean4/ApiTypes.lean`) | open | ungraded | — | — | —
|===

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the repository-specific ABI claims

When the estate census consumes this new per-claim table, it sees only the seven generic obligations because the table closes here. However, verification/proofs/idris2/MANIFEST lines 14–19 explicitly require the three gated src/interface/Abi/ obligations to be restated in PROOF-STATUS.adoc; omitting them makes the advertised one-row-per-claim census incomplete. Add claims for those repository-specific proofs, along with their current tokens and receipts.

Useful? React with 👍 / 👎.

Comment on lines +71 to +72
`.machine_readable/coaptation/README.adoc`). No row in the Claims table rests on
this bridge.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Record the active TLA+ policy exception

The new trust-boundary inventory ends after the Coaptation assumption, but verification/proofs/README.adoc lines 43–48 explicitly identifies tlaplus/ as a §4 exception that must also be recorded in PROOF-STATUS.adoc, and verification/proofs/tlaplus/StateMachine.tla lines 9–12 records that exception beside the artifact. Audits that rely on this section will therefore miss an exception present in the repository; list it here without treating the shipped example as proof evidence, and state that no claim rests on it if that remains the case.

Useful? React with 👍 / 👎.

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