Repository navigation
claims/graph: reconcile H3-RUNG-FLOOR with the claims gate (binding + operational grade) - #171
Merged
cursor[bot] merged 3 commits intoSep 27, 2026
Conversation
#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>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
cursor
Bot
merged commit Sep 27, 2026
d4ad3bb
into
chatgpt/drive-github-hardening-20260919
4 of 5 checks passed
cursor
Bot
deleted the
cursor/hardening-rung-floor-source-binding-ac93
branch
September 27, 2026 19:29
This was referenced Sep 27, 2026
This was referenced Sep 27, 2026
This was referenced Oct 15, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Corrects a defect I introduced by merging #111 while its
verifycheck was still failing atclaims_gate_adapter.py event-compare. Since 8e2eda4 every transition onchatgpt/drive-github-hardening-20260919has been refused:UNRESOLVED_CONTROLLING_SOURCE/binding_kind:unresolved_prose: H3-RUNG-FLOOR is gradedCERTIFIED_RUNG, whichSOURCE_CONTROLLING_HINTStreats as controlling, and itssourcefield was prose only, so the gate could not bind bytes for it.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.jsononly (plus one test):source_bindingsfor H3-RUNG-FLOOR to the frozen carrierengine/rn_engine/frozen/K3_SIDE24_LB/UPPER2D/H3_closure/H3_RUNG_FLOOR.md(whole_file, expected sha2566347275d…440dfa, 7,003 B, carrier RNENG-08), with the sameexternal_sync_obligationfreshness the other precise bindings declare.AUTHOR_SIDE_CERTIFIEDwithsource_grade_verbatim: CERTIFIED_RUNGandaudit_disposition: LABEL_PRESERVED_NOT_CONTROLLING, following the graph's existing fail-closed audit convention (D1-v2.2(1)). SameGRADE_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.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
Status discipline
Verification
Python 3.11.16, locked pytest 9.0.2:
claims_gate_adapter.py event-comparewithCLAIMS_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=0math_status_check: problems=0 disposition=OPEN_HOLD independence_credit=0tests/test_claims*.py tests/test_math_status*.py tests/test_attestations.py: 242 passed, 3 subtestsclosure_pipeline check-plan: PASSScientific 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.