Issue 112 retrieval: RW/BBW finite criterion vs exact wrapping/M tables (Phase 0) - #685
Draft
LightChainr wants to merge 1 commit into
Draft
Issue 112 retrieval: RW/BBW finite criterion vs exact wrapping/M tables (Phase 0)#685LightChainr wants to merge 1 commit into
LightChainr wants to merge 1 commit into
Conversation
Phase 0 feasibility note answering the five issue questions with verbatim primary-source quotes (RW PRE 76 011110 checked from arXiv PDF; BJSS arXiv:2206.12335 Theorem 1.3 checked from arXiv HTML v2; BBW CPC 21 bibliographic data from Cambridge Core). Verdict: methodologically interesting but weak — the repo's torus wrapping/M tables are the wrong observable family for the open-boundary block event; exact enumeration dies at s=3; output is necessarily a rigorous CI, not a deterministic theorem. Adds the three missing references.bib entries.
Owner
Author
|
Verification comment, not a merge request. Ticket stays open. Phase 0 as assigned: notes + bib, no production, no new MC, no STATUS, no #636. Five questions each have a carrier. Keep:
Caveat: BBW 2012 full text is marked NOT FOUND this session (Cambridge Core bibliographic only). The usable quotes are RW 2007 and BJSS 2022, which is enough for Phase 0. Do not close #112. |
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 nothing; addresses the re-queued Phase 0 retrieval slice of #112 (parent stays open).
Scope
Retrieval/feasibility only — no production implementation, no new Monte Carlo, no #636, no STATUS edit. One notes file + references.bib gap-fill.
Deliverable
notes/rw-bbw-vs-wrapping-tables-20260908.mdanswers the five issue questions with verbatim primary-source quotes:p_max(Z^2) <= 0.8457(verified verbatim from arXiv HTML v2).2s x sunique-largest-cluster block event (quoted), strictP_p(E_e) > 0.8457, exact binomial tail at per-run alpha1/6000000; 2007 N=400/M>=378 tail quoted and reproduced exactly by the merged gate.[0.5925,0.5930]; heuristic s^-3/4 law gives ~8.6x linear / ~73x area for width 1e-4. Any achievable interval is dominated by existing 9–10-digit estimates — no scientific improvement on offer.Outcome
Methodologically interesting but weak (matches the #278 classification). Recommendation: keep #112 parked; the only unmerged work is the #278 production gate (exploratory placement + one fresh pre-registered run), not justified now.
References
Adds the three missing bibtex entries:
RiordanWalters2007RigorousCI(primary read from arXiv PDF 2026-09-08),BalisterBollobasWalters2012OneIndependent(bibliographic data from Cambridge Core; full text NOT FOUND/unchecked this session),BalisterJohnstonSaveryScott2022Improved(primary read from arXiv HTML v2).Verification
scripts/rigorous_pc_confidence_gate.pyruns clean on the current tree.