audit(#570): underflow-bound follow-up — re-run on merged main, P50 staleness measured - #687
Draft
LightChainr wants to merge 1 commit into
Draft
audit(#570): underflow-bound follow-up — re-run on merged main, P50 staleness measured#687LightChainr wants to merge 1 commit into
LightChainr wants to merge 1 commit into
Conversation
…ess measured The 2026-09-05 audit was conditional on unmerged PR #564; #564 landed via PR #573, so the condition is resolved. Re-checked every section on current main and re-ran the one gap in the old note as a measurement instead of a classification argument: - P43 primary_score.json replays byte-identical (sha256 match), and the private float tail sits 1.9e-15 / 3.2e-15 from exact at N=185/265. - P50 score.json IS tail-derived (imports project_size / P49 helpers) and the 09-05 note missed it: replay moves 72/104 leaves, worst 1.25e-3 on a correlation-eigenvalue diagnostic; every verdict-bearing leaf in the frozen report table is intact to reporting precision. Measured, not regenerated. Verdict unchanged and now unconditional: nothing was capped, nothing stale that moves a verdict. Draft PR against main; does not close #570.
Owner
Author
|
Verification comment, not a merge request. Ticket stays open. Notes-only, no STATUS, no production, no new Monte Carlo. Four checks from #570 are answered: no geometry died on the silent zero; one latent private I did not re-run the scorers; this is a scope/structure verify of the note. Do not close #570. |
Owner
Author
|
Grok verify (independent of the CLI self-check). Not a merge. Ticket stays open. Tripwire vs #570:
|
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 the gap in the 2026-09-05 audit of #570. Notes-only; no code, no data, no STATUS, ticket stays open.
What changed since that audit
8b5bc84) and stands.results/server-20260829/P50-n145-n290-fullcurve/analysis/score.json:score_p50_fullcurve_n290.pyimportsproject_sizeand the P49 helpers, so that committed score is tail-derived.The measurement (per the ticket: measure the move, don't regenerate a dated reveal)
primary_score.json— replays byte-identical (sha2563a545e6c…, 83/83 leaves). Its private floattailis1.9e-15/3.2e-15from Fraction-exact at N=185/265, four orders below the P49 gate's worst leaf move. Latent-only past ~790 sites, as already flagged.score.json— replay through the merged anchored routine moves 72/104 leaves, worst1.25e-3oncorrelation_eigenvalues[0](a diagnostic). Every verdict-bearing leaf in the frozen REPORT.md table is intact to reporting precision (χ² 9.35200 → 9.3520036; all four z's within 5e-5). No sign, no σ-distance, no verdict moves.Answer to the ticket's four checks (unchanged, now unconditional)
score_issue43_full_curve.py::tail), everything else mpmath/exact/q-series/small-n — safe.File:
notes/underflow-bound-followup-quantified-20260908.md.