Skip to content

claims/graph: reconcile H3-RUNG-FLOOR with the claims gate (binding + operational grade) - #171

Merged
cursor[bot] merged 3 commits into
chatgpt/drive-github-hardening-20260919from
cursor/hardening-rung-floor-source-binding-ac93
Sep 27, 2026
Merged

cursor[bot] merged 3 commits into
chatgpt/drive-github-hardening-20260919from
cursor/hardening-rung-floor-source-binding-ac93

Conversation

@d6g8k5htny-coder

Copy link
Copy Markdown
Owner

What this changes

Corrects a defect I introduced by merging #111 while its verify check was still failing at claims_gate_adapter.py event-compare. Since 8e2eda4 every transition on chatgpt/drive-github-hardening-20260919 has been refused:

  • UNRESOLVED_CONTROLLING_SOURCE / binding_kind:unresolved_prose: H3-RUNG-FLOOR is graded CERTIFIED_RUNG, which SOURCE_CONTROLLING_HINTS treats as controlling, and its source field was prose only, so the gate could not bind bytes for it.
  • Against the pre-docs(rn): walk-down over-claim scope fixes (RN-UNIF ledger §2) #111 base (38a3e07) the same node is also UNSUPPORTED_CONTROLLING_PROMOTION: a new controlling node introduced by merge, which the gate refuses by design ("loss-only refusal, not a positive mathematical admission mechanism").

Fix, in claims/graph.json only (plus one test):

  1. source_bindings for H3-RUNG-FLOOR to the frozen carrier engine/rn_engine/frozen/K3_SIDE24_LB/UPPER2D/H3_closure/H3_RUNG_FLOOR.md (whole_file, expected sha256 6347275d…440dfa, 7,003 B, carrier RNENG-08), with the same external_sync_obligation freshness the other precise bindings declare.
  2. Operational grade AUTHOR_SIDE_CERTIFIED with source_grade_verbatim: CERTIFIED_RUNG and audit_disposition: LABEL_PRESERVED_NOT_CONTROLLING, following the graph's existing fail-closed audit convention (D1-v2.2(1)). Same GRADE_STRENGTH (3), zero independence credit; the note records why. A merge is not a positive admission; a nonauthor review filed against the node is the route to the verbatim label.
  3. tests/test_claims_firewalls.py: restores the "no operational CERTIFIED_RUNG in the committed graph" control (which claims_check: read H3-RUNG-FLOOR's interval declaration; reconcile prose count #169 had rewritten to pin the docs(rn): walk-down over-claim scope fixes (RN-UNIF ledger §2) #111 state) and asserts the verbatim label is preserved.

Type of change

  • Tooling, tests or CI
  • Claim-graph transcription (no status promotion; an operational grade is recorded below the object's own label)

Status discipline

  • No claim status was promoted
  • Frozen bodies not edited in place

Verification

Python 3.11.16, locked pytest 9.0.2:

  • claims_gate_adapter.py event-compare with CLAIMS_GATE_BEFORE_REF ∈ {38a3e07 (pre-docs(rn): walk-down over-claim scope fixes (RN-UNIF ledger §2) #111), 8e2eda4, e7652a1} → HEAD: rc=0, transition_ok=true, no transition errors in all three. Before this branch, all three refused on H3-RUNG-FLOOR.
  • claims_check: claims=27 premises=13 firewalls=10 enforced=10 problems=0
  • math_status_check: problems=0 disposition=OPEN_HOLD independence_credit=0
  • tests/test_claims*.py tests/test_math_status*.py tests/test_attestations.py: 242 passed, 3 subtests
  • closure_pipeline check-plan: PASS

Scientific effect: NONE. RN3-FAR and RN5-NEAR-POINT-CERTS still depend on H3-RUNG-FLOOR as #111 intended; only the gate-visible grade channel changes.

Open in Web Open in Cursor 

cursoragent and others added 3 commits September 27, 2026 19:08
#111 added H3-RUNG-FLOOR (CERTIFIED_RUNG, controlling) with a prose-only
source field. claims_gate_adapter binds controlling sources at every
transition and refused with UNRESOLVED_CONTROLLING_SOURCE, so event-compare
failed for every commit on the hardening branch after 8e2eda4.

Add a source_bindings entry to the frozen carrier
engine/rn_engine/frozen/K3_SIDE24_LB/UPPER2D/H3_closure/H3_RUNG_FLOOR.md
(whole_file, expected sha256 6347275d..., 7,003 B, RNENG-08), with the same
external_sync_obligation freshness the other precise bindings declare.
Transcription only; no grade, flag or independence credit moves.

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
…label preserved verbatim

claims_gate_adapter treats CERTIFIED_RUNG as a controlling status and
refuses a new controlling node introduced by merge
(UNSUPPORTED_CONTROLLING_PROMOTION); #111's PR CI failed on exactly this
and was merged regardless. Follow the graph's fail-closed audit convention
(D1-v2.2(1)): keep the object's label in source_grade_verbatim, record the
operational grade as AUTHOR_SIDE_CERTIFIED (same GRADE_STRENGTH, zero
independence credit), audit_disposition LABEL_PRESERVED_NOT_CONTROLLING.
A merge is not a positive admission.

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
…t verbatim

Co-authored-by: Dylan Roy <d6g8k5htny@privaterelay.appleid.com>
@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