Repository navigation
Research: certified bit-side lever budgets for PR589 at a = 1/99 under the proposed revision 3 (no new kappa) - #1334
Merged
Mister-Meeseeks merged 3 commits intoOct 14, 2026
Conversation
added 3 commits
October 14, 2026 04:26
…it supplier at a = 1/99 (no new kappa)
…der the row bounds), O2 holds at depth <= 3, correct the window overclaim and floor comparisons
Contributor
|
100-PR batch review at Merged to Reviewed scope: Certified bit-side lever budgets at a=1/99, rebuilding the retained histogram and comparing explicit coverage, copy and idle-cap relaxations. Infeasible relaxed rows are scoped obstructions; favorable rows are unconstructed targets, not new κ witnesses. The pinned scoped command passed; the batch ledger contains its command, input hashes, environment and log. This incorporates the research/tooling contribution and does not change the selected κ or discharge the inherited multiplication-theorem assumptions. Batch review, attribution and evidence. Thank you for the contribution. |
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.
This PR has scoped obstructions and a screening table. There is no new κ, and the selected record is unchanged.
bit-helper-contract, with the scope changed. The card question is saturated, and the register-model card is done in Research theorem: exact paid cost for binary affine register words #1333.bce54fb3.Why
The proposed priority revision 3 (open #1272, stacked on open #1240) prices the centre-path, rank-shape and coverage-law levers for the complex supplier only. This PR adds the bit-side numbers for the selected PR589 supplier.
Model and premises
The arithmetic uses exact rational intervals, standard library only, and imports no repository engine.
It is #1240's coverage-law relaxation, applied to the bit side:
The idle cap is a premise tied to the halving depth.
global_k.pyraises the halving depth until 2·maxchild^HD < m^HD.row_bound.py) admits HD ≤ 4, which gives caps 50 and 53.Results (certified at a = 1/99)
The fail rows also fail at caps 50, 53 and 63.
O1 (copy charge 63).
O2 (centre path shared, copy charge 31.5, full-frame width-8 helpers).
Joint surface. The README has the table of copy charge × full-frame helper count at caps 45, 50 and 53, for ideal and shipped data shapes.
What it does not say.
Complex side.
Checks
PR589-EXPECTED.json→ bit word, endpoint, halving depth and row coefficient. The row-bound and halving-depth source lines are pinned.Reproduce
python3 -I -B research/bit-revision3-levers-seed03/verify.py # ~13 s; PASS_BIT_REVISION3_LEVERS python3 -I -B -m unittest discover -s research/bit-revision3-levers-seed03 -p test_package.py python3.12 scripts/research_package.py --package research/bit-revision3-levers-seed03Overlap
Disclosure
Prepared by Sagar Thakrar (thakrarsagar) with substantial AI assistance from Claude (Anthropic) via Claude Code. Parallel read-only scout and judge subagents ranked the question. A post-PR adversarial review found the halving-depth error and two overclaims; all are corrected in the second commit. No claim was posted to Discussions. Apache-2.0.