[p569] Verify height-4 second-implementation extension (independent re-run) - #742
Draft
LightChainr wants to merge 1 commit into
Draft
LightChainr wants to merge 1 commit into
LightChainr wants to merge 1 commit into
Conversation
…e-run) Independent re-run by compute1 of the already-parameterized degree-≤6 second implementation at height 4 across all four frozen intervals, plus the agreement harness. Per-degree class sizes [23,265,2639,24913,229703,2093785], total 2,351,328; all four intervals excluded with 0 screen survivors; agreement 48/48 cells across heights 3 and 4. Honesty disclosure: the height threading was already present in main and the height-4 artifacts were already committed; this caller did not edit the replication script. See notes/p569-degree6-height4-replication-verification.md. Full Matching-One repository CI has not been run for this commit.
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
1 participant
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.
Issue #569 — height-4 extension of the degree-≤6 second implementation
This is an independent verification by compute1, not a fresh implementation of the height-4 census.
What the re-run confirmed
scripts/degree6_independent_replication.py <id> --height 4for all four frozen intervals.[23, 265, 2639, 24913, 229703, 2093785], total 2,351,328 — matches the ticket expectation exactly.excluded = True,screen_survivors_total = 0(certified mean-value screen retains zero candidates at every degree).scripts/degree6_implementation_agreement.py:heights_compared = [3, 4],cells_compared = 48,cells_in_agreement = 48,implementations_agree = True; closest-member residual gap within mean-value allowance for every interval.Honesty disclosure (required by the ticket)
The ticket's premise — that only the artifact field hardcodes
HEIGHTand an outside caller must mechanically threadheight, weakening the independent-author property — does not hold in the currentmain. On inspection:scripts/degree6_independent_replication.py:288already reports"coefficient_height_max": height(the parameter, not theHEIGHTconstant); the whole module was already parameterized byheight.results/pslq-degree6-height4-{id}/andresults/pslq-degree6-height4-replication-{id}/) are already committed inmain.scripts/degree6_implementation_agreement.pyalready enumeratesHEIGHT_DIRS = {3, 4}.Therefore this caller did not edit the replication script. The height-4 extension was already present in
mainbefore this assignment. The independent-author property of the code-writing step is intact; this assignment is a verification, not an authorship change. Maintainers should reconcile this with the ticket's premise (the height-4 extension appears already completed inmain).Files added (no existing files modified)
notes/p569-degree6-height4-replication-verification.mdresults/pslq-degree6-height4/p569-verification/{REPORT.md,metadata.json,commands.txt}Full Matching-One repository CI has not been run for this commit.