Skip to content

Prove exact contiguous helper storage: 5q versus peak 4q (no new κ) - #5897

Merged
Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
petalas:research/w1-1022z-rank-obstruction
Oct 27, 2026
Merged

Mister-Meeseeks merged 1 commit into
CrocSwap:mainfrom
petalas:research/w1-1022z-rank-obstruction

Conversation

@petalas

@petalas petalas commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Prove an exact storage obstruction for eight fixed half-open helper lifetimes. For every positive real scale q:

peak live width                 4q
minimum with split fixed sets   4q
minimum with contiguous blocks  5q

Claim type: scoped mathematical proof with finite corroboration. The explicit family forces a 25% storage surcharge even when all lifetimes are known in advance. A real-to-integer compression lemma and a four-cell contradiction prove the lower bound; displayed layouts attain both optima.

This takes the contiguous-block boundary explicitly excluded by Ali Romman's PR #5763 at cee2336bc3a20c586b1dbb55152d97a114c657a6. The predecessor is cited as the question source and split-range context, not audited or replayed. Classical dynamic storage allocation is credited; novelty of the general fragmentation phenomenon is not claimed. This result was produced by Nick Petalas.

Evidence

  • Before: peak live width alone provides no contiguous layout certificate under the changed contract.
  • After: the explicit family has exact optima 4q and 5q. The verifier checks all 40,320 total address orders, independently excludes all 9,216 capacity-four integer placements, validates both layouts at six exact rational scales, and rejects four invalid layouts.
  • CPython 3.12.15 warning-strict normal and optimized runs pass with PASS_CONTIGUOUS_HELPER_STORAGE_GAP, timed locally at 0.52s and 0.53s. Both registered VERIFY commands and package metadata checks pass.
  • Committed bytes and declared source history pass at d46194d7f001210e49ef155409b76182c773e6e7. A generated local receipt binds all five package hashes. Read-only review found no mathematical error in the new proof or layouts.

From the checkout root:

/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -W error -B research/contiguous-helper-storage-gap/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -O -W error -B research/contiguous-helper-storage-gap/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/research_package.py --package research/contiguous-helper-storage-gap
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/check_research_commit.py --package research/contiguous-helper-storage-gap --check-source-history

Elsewhere, substitute a CPython 3.12 interpreter for the absolute interpreter path. Standard library only.

Limitations

The proof fixes lifetimes, widths and addresses throughout each lifetime. It does not permit movement, change chronology, prove a smallest obstruction, or establish a worst-case approximation ratio. The all-positive-real statement has a written proof; finite enumeration corroborates its unit instance.

No actual supplier is asserted to require contiguous blocks. Source-specific cleanup, routing, ownership, precision, tape movement and all-size compiler obligations are unrun and outside this claim. No native construction, new kappa, selected-frontier change or complete multiplication theorem is claimed. Independent human and formal proof-kernel review are unclaimed.

Related open work

Open next questions

  • Can an actual native caller use split fixed ranges with its complete route and address-description bill? Start with a source-pinned access trace and a declared movement contract.
  • Which source-derived lifetime restrictions guarantee contiguous storage at peak width? First identify a restriction that excludes this eight-helper pattern.

CI notes

Head: d46194d7f001210e49ef155409b76182c773e6e7. Run 40500640359 completed with plan failed and replay skipped.

The plan job failed only in Onboarding helper tests, in the unchanged tests/test_research_current_assignment.py: FAILED (failures=8, errors=2, skipped=22). The two errors are KeyError: 'follow_up_steps' and KeyError: 'catalog_first_step'; the eight failures concern current/historical first-step metadata and sparse-reference expectations. The same step, test file and eight-failure/two-error result were also checked in PR #5896's plan job, based on the same canonical main de5ec2e7a6074068452f45b1a191b5c72832df4a.

The package replay job was skipped. Hosted replay has not certified this package. Only the local mathematical and package checks listed above have run. This PR changes none of those shared tests or helpers; their repair is left to maintainers.

Merge Danger

Door: two-way. Five new files are isolated in research/contiguous-helper-storage-gap/.

Blast radius: research. No shared code, selected record or predecessor files change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants