fix(#80): A1 PUBLICATION_GRADE requires a positive symmetrised-gap certificate, not F1-F5 threshold exhaustiveness - #90
Merged
Conversation
…gap certificate (#80) The A1 early branch awarded CONFIRMED/PUBLICATION_GRADE (0.95) whenever gap_rate_consistency < 0.05 + single-exp held and none of the F1-F5 thresholds fired -- resting a publication-grade claim on the unprovable exhaustiveness of the threshold set (residual flagged independently by both #79 reviewers). A weakly-non-normal gap failure below all thresholds with a single-exp-at-gap trajectory would have self-certified. Fix (issue #80 to-do 2, burden of proof reversed): - new evidence key sym_gap_corroborated: 1.0 iff a MEASURED symmetrised gap shows no F3-grade reduction (certified GNS gap_to_gns_ratio <= 1.2, or KMS gap_to_kms_ratio <= 1.2), fail-closed on floored/uncertified gaps - A1 confidence: 0.95 only with the certificate; uncorroborated A1 caps at 0.70 -> CANDIDATE/CONFIRMATION - gap_to_kms_ratio graduates from advisory (#89) to class-influencing; an F3 veto off it stays deferred to its own FP study Anchor-preserving: the gap-controlled thermal reference has Delta_GNS = Delta_KMS = Delta exactly (stays 0.95/CONFIRMED); V1-V5 golden labels (A5/A11) never take the A1 confidence path. New synthetic adversary, KMS-certificate and double-floored fail-closed tests. Gates: pytest 489 passed (anchors 21/21 incl. QuTiP), ruff clean, mypy clean. claim_status: pending until cross-family review confirms the semantics. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BuG9j9cRJ6x6QMuYk7vXdx
marcohost33-maker
marked this pull request as ready for review
July 7, 2026 15:07
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.
Closes #80.
Summary
Dedicated classification-semantics PR (AGENTS.md §3); the twin of #89/#88 and the implementation of #80 to-do 2 (reverse the burden of proof). The A1 early branch awarded CONFIRMED / PUBLICATION_GRADE (0.95) whenever
gap_rate_consistency < 0.05+ single-exp held and none of the F1–F5 thresholds fired — i.e. the publication-grade claim rested on the unprovable exhaustiveness of the threshold set (kreiss>5, petermann>5, henrici>1, trans>5, reach>2·ratio, gns>1.2). Both independent #79 reviewers (Equalita facts-PASS; cross-family gpt-5.5 ADEQUATE) flagged exactly this residual: a hypothetical weakly-non-normal gap failure below all thresholds with a single-exp-at-gap trajectory would self-certify at publication grade.Physics rationale
A measured symmetrised gap equal to the spectral gap is operator-intrinsic positive evidence of gap control: it certifies exponential contraction at rate ~Δ in the GNS (Mori-Shirai) or KMS (Fagnola s=1/2) geometry. Any genuine symmetrised-gap-failure mechanism — including a weakly non-normal one below all F1–F5 thresholds — must show up as a reduction (or an uncertifiable floor) in these measured quantities. So:
sym_gap_corroborated= 1.0 iffgap > 0and (certified GNS withgap_to_gns_ratio ≤ 1.2orgap_to_kms_ratio ≤ 1.2). The 1.2 boundary is deliberately the F3 firing threshold — "corroborated" and "F3-grade reduction" are complementary, no gap in between. Floored/uncertified GNS (fix(#88): classifier gates A2/F3 on a certified GNS gap — floor sentinel no longer self-certifies PUBLICATION_GRADE #89) and floored KMS both fail, fail-closed._confidence: A1 scores 0.95 only with the certificate; uncorroborated A1 caps at 0.70 → CANDIDATE / CONFIRMATION — the honest grade: the single-exp-at-gap observable is measured, operator-intrinsic gap control is not.gap_to_kms_ratiograduates from advisory (fix(#88): classifier gates A2/F3 on a certified GNS gap — floor sentinel no longer self-certifies PUBLICATION_GRADE #89) to class-influencing — exactly the "dedicated PR with FP coverage" the advisory contract demanded. Using it as an F3 veto (issue Classifier F3 (A2/CONFIRMED/PUBLICATION_GRADE) fires off the gns_gap conservative-floor sentinel, not a measured symmetrised-gap reduction #88 option 2) remains deferred.Behaviour change
Δ_GNS = Δ_KMS = Δ)Anchor-preserving: the gap-controlled reference keeps A1/none CONFIRMED (its symmetrised gaps equal Δ exactly — verified numerically); V1–V5 golden labels are A5/A11 and never take the A1 confidence path; sacred anchor suite 21/21 green. No known real system flips — the capped region is precisely the adversarial class both reviewers hypothesised.
Remaining from #80 (not in this PR)
Test plan
pytest -q— 489 passed (exit 0)pytest tests/test_anchors.py -v— 21/21 incl. QuTiP cross-checks (exit 0)ruff check src tests benchmarks— clean (exit 0)mypy src/liouscope— clean, 50 files (exit 0)CHANGELOG.mdupdated (Unreleased → Fixed)Merge authorized by User1/Marco (Session 2026-07-07, „abarbeite weitere issues und merge") on green required checks; post-merge cross-family review of the semantics stays open in the #80 thread (
claim_status: pending, KANON anchorRESEARCH-LIOUSCOPE). No manifest-schema, taxonomy-version or CITATION.cff change (same footprint as #77/#85/#89). No history-touching git operations.🤖 Generated with Claude Code
https://claude.ai/code/session_01BuG9j9cRJ6x6QMuYk7vXdx
Generated by Claude Code