Skip to content

claims_check: read H3-RUNG-FLOOR's interval declaration; reconcile prose count - #169

Merged
cursor[bot] merged 1 commit into
chatgpt/drive-github-hardening-20260919from
cursor/hardening-claims-vocab-rung-floor-ac93
Sep 27, 2026
Merged

cursor[bot] merged 1 commit into
chatgpt/drive-github-hardening-20260919from
cursor/hardening-claims-vocab-rung-floor-ac93

Conversation

@d6g8k5htny-coder

Copy link
Copy Markdown
Owner

What this changes

Repairs a red claims_check on chatgpt/drive-github-hardening-20260919 created by the interaction of two independently green PRs: #134 (closed arithmetic vocabulary, AMBIGUOUS classification) and #111 (H3-RUNG-FLOOR added to claims/graph.json, claims 26 → 27). On the merged tip 8e2eda4 the checker reported problems=3:

  • FW-FLOAT-NOT-CERTIFIED ×2: H3-RUNG-FLOOR's evidence declaration interval (mpmath iv, 100 dps) classified as AMBIGUOUS, because the fixed string contains the float prose hint mpmath.
  • claims/README.md does not state '27 claims'.

Fix:

  • tools/claims_check.py: add the certificate's verbatim declaration interval (mpmath iv, 100 dps) to EXACT_ARITHMETIC_DECLARATIONS, following the checker's own rule that a new suffix form is placed explicitly. mpmath's iv context is directed-rounding interval arithmetic, distinct from the mp float context the FLOAT set lists as mpmath. The vocabulary stays closed (one explicit string; disjointness test still passes).
  • claims/README.md: 27 claims.
  • tests/test_claims_firewalls.py: three controls pinned pre-docs(rn): walk-down over-claim scope fixes (RN-UNIF ledger §2) #111 facts. They now pin the current graph: evidence_arithmetic_unreadable=2 (BINDING sentence plus H3-RUNG-FLOOR's carrier prose not applicable (Markdown artifact)), H3-RUNG-FLOOR is the sole CERTIFIED_RUNG with empty depends_on (FW-RUNG-OPEN-PREMISE is live, not inert), and the drifted-count control derives the number from the graph.

Type of change

  • Tooling, tests or CI

Status discipline

  • No claim status was promoted
  • Frozen bodies not edited in place
  • claims/graph.json not modified

Verification

Python 3.11.16, locked pytest 9.0.2, on this branch:

  • tools/claims_check.py: claims=27 premises=13 firewalls=10 enforced=10 evidence_arithmetic_unreadable=2 certifying_without_evidence=1 problems=0
  • tests/test_claims*.py: 181 passed, 3 subtests (two clean runs; one earlier run had a single test_claims_gate_enforcement.py CLI case fail on a subprocess timeout, a pre-existing timing sensitivity seen on the untouched base as well)

Scientific effect: NONE.

Open in Web Open in Cursor 

…ose count

Merging #134 (closed arithmetic vocabulary) and #111 (H3-RUNG-FLOOR added
to the graph) onto the hardening branch left claims_check at problems=3:
the evidence declaration 'interval (mpmath iv, 100 dps)' classified as
AMBIGUOUS because the fixed string contains the float hint 'mpmath', and
claims/README.md still said 26 claims.

- Add the certificate's verbatim declaration to EXACT_ARITHMETIC_DECLARATIONS
  (mpmath's iv context is directed-rounding interval arithmetic, not the mp
  float context). Closed vocabulary preserved: one explicit string.
- claims/README.md: 27 claims.
- tests/test_claims_firewalls.py: three controls pinned pre-#111 facts
  (unreadable=1; no CERTIFIED_RUNG claim; literal '26 claims'). They now
  pin the current graph: unreadable=2, H3-RUNG-FLOOR is the sole
  CERTIFIED_RUNG with empty depends_on, count derived from the graph.

claims_check: claims=27 premises=13 firewalls=10 enforced=10 problems=0.
No grade, gate or independence credit moves.

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
@cursor
cursor Bot merged commit cad99e2 into chatgpt/drive-github-hardening-20260919 Sep 27, 2026
3 of 5 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

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.

2 participants