Skip to content

docs(proofs): report proof census as a count, not a percentage - #77

Open
hyperpolymath wants to merge 1 commit into
mainfrom
claude/proof-policy-drift
Open

hyperpolymath wants to merge 1 commit into
mainfrom
claude/proof-policy-drift

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

PROOF-POLICY §8.4 (standards 3-practice/PROOF-POLICY.adoc): a proof census is reported as a count with its denominator, never as a percentage. docs/status/PROOF-STATUS.adoc line 23 carried the template's bare 0% proven.

Changes

  • docs/status/PROOF-STATUS.adoc line 23: *Overall*: 0% proven becomes *Overall*: 0 of 7 proven. The 7 is the Total row of the same file's summary table (ABI 5, TP 2). No number was invented.

RSR Quality Checklist

Required

  • No banned language patterns
  • No licence text or SPDX headers touched
  • No secrets, credentials, or .env files included
  • Tests: not applicable, one documentation line

Testing

ruby $(gem contents asciidoctor | grep 'bin/asciidoctor$') -o /dev/null --failure-level=WARN docs/status/PROOF-STATUS.adoc exits 0.

Skipped: nothing. Draft, not merged.


Generated by Claude Code

PROOF-POLICY §8.4: a census is a count with its denominator.
Replace the bare "0% proven" line with "0 of N proven", N taken from
the Total row of the same file's summary table.

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

coderabbitai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Summary

Summary by CodeRabbit

  • Documentation
    • Updated the reported proof status from “0% proven” to “0 of 7 proven” to show the number of proven items alongside the total.

The overall proof status changes from a percentage to a count. It now reports “0 of 7 proven”.

Changes: Proof status

Layer / File(s) Summary
Update proof status display
docs/status/PROOF-STATUS.adoc
The overall proof status changes from a percentage to “0 of 7 proven”.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: Minimal · up to 65fd1

This documentation-only edit changes the proof status line from a percentage to a count with its denominator. It has no runtime impact and is safe to merge.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: the proof census in PROOF-STATUS.adoc is reported as a count instead of a percentage. The raw summary confirms the only edit is the Overall line, changed from 0% prove…
Description check Passed The description covers the summary, the specific change with its source of the denominator, the testing command and result, and the checklist. It follows the template's main sections. Required checkli…
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.
Full details: Title check

Explanation

The title names the main change: the proof census in PROOF-STATUS.adoc is reported as a count instead of a percentage. The raw summary confirms the only edit is the Overall line, changed from 0% proven to 0 of 7 proven. The title is specific, concise, and matches the changeset.

Full details: Description check

Explanation

The description covers the summary, the specific change with its source of the denominator, the testing command and result, and the checklist. It follows the template's main sections. Required checklist items are partly ticked, and the Tests item is marked not applicable with a reason. The template's Changes, Testing, and checklist structure is present. The 'As Applicable' section and the Screenshots section are omitted, which is non-critical for a one-line documentation change. The description does not use the template's HTML comments, which is acceptable. Missing items are minor.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 7a9b5d90-4840-4c0e-90eb-79140053cb70
Commits

Reviewing files that changed from the base of the PR and between 8c833fb and 65fd1c7.

Files selected for processing: 1

  • docs/status/PROOF-STATUS.adoc

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

Recent review details

Context from checks skipped due to timeout: 11

  • GitHub Check: CodeRabbit
  • GitHub Check: Groove manifest check
  • GitHub Check: docs
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Validate DEED manifests
  • GitHub Check: check
  • GitHub Check: Validate K9 contracts
  • GitHub Check: analyze (actions, none)
  • GitHub Check: openssf-compliance
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: estate-rules

@sonarqubecloud

Copy link
Copy Markdown

@linear-code
linear-code Bot marked this pull request as ready for review November 17, 2026 22:19
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