Skip to content

Coalesce a P104 owned copy: one fewer field and twelve fewer scalar units (no κ) - #6154

Merged
Mister-Meeseeks merged 2 commits into
CrocSwap:mainfrom
petalas:research/w9-1022ak-helper-delivery
Oct 28, 2026
Merged

Mister-Meeseeks merged 2 commits into
CrocSwap:mainfrom
petalas:research/w9-1022ak-helper-delivery

Conversation

@petalas

@petalas petalas commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Finite exact circuit certificate and scoped substitution proof, produced by Nick Petalas. Coalesce owned register 770 with its existing source 791 in DreamingOfClouds' PR #6144 word. After the source's last frame-549 read, it performs the duplicate's continuation itself.

- local scalar units 189658; events 22818
+ local scalar units 189646; events 22815
- declared owned fields 29; owned lifetimes 31
+ declared owned fields 28; owned lifetimes 30

Peak live ownership remains 13. Public endpoints, all paid ranks and all productive ranks are retained. No new kappa, physical peak-space bound, supplier admission or complete multiplication theorem is claimed.

Package: research/owned770-descent-pruning/. PROOF.md gives the exact last-read substitution argument; construct.py deterministically emits the new word; RESULT.json is generated and bound to every package source. The unchanged predecessor word is retained in publication ancestry, with its original head, path, blob and SHA256 in PREDECESSOR.json.

The initial CLAIM targeted an interior descent-stage deletion, following JosieElliston's read-rerouting question in #6136. That paid-profile deletion was not obtained. The first smaller verified improvement was shipped instead. Frames 553 and 1047 remain in the coalesced trajectory. This changes owned lifetime identity, rather than replaying a predecessor census or repeating fixed-word scalar resynthesis.

Evidence

Before, INIT/COPY/SCALE created a second owned value while its source was left unread until CLEAR. After, the source is scaled in place and performs the same descent and reads. Removing one INIT, coefficient-one COPY and CLEAR saves exactly 2+8+2 = 12 scalar units.

Local CPython 3.12.15 on macOS 27.0.1 arm64 passes:

  • Complete exact forward endpoint/ownership replay and a separate dense reverse replay on all 798 input columns and 636804 coefficients. All 770 arbitrary public inputs are retained; one initialized owned coordinate is deleted.
  • Literal enumeration of all event prices and paid ranks; equal native frame-boundary multisets and public boundaries; nine rejected faults covering lifetime, scaling, read, descent and source-use conditions.
  • Warning-strict normal and optimized direct checks, timed at 2.135 s and 1.896 s. Each registered check is below five minutes; both registered checks together pass in 4.139 s. These are timeout measurements, not a performance claim.
  • PASS_REGISTERED_RESEARCH_PACKAGE; exact committed bytes and source-history preflight for all 11 files; official committed export integrity and all three declared inputs; normal and optimized Git-free export replay.

Exact reproduction from the repository root:

/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -W error -I -B research/owned770-descent-pruning/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -W error -I -O -B research/owned770-descent-pruning/verify.py
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/research_package.py --package research/owned770-descent-pruning
/Users/nick/git/integer-mult-bounds/.venv/bin/python3.12 -B scripts/check_research_commit.py --package research/owned770-descent-pruning --check-source-history

A clean CPython 3.12 interpreter may replace the local path. Expected direct output is PASS_OWNED_LIFETIME_COALESCENCE columns=798 coefficients=636804 controls=9 scalar_saved=12.

Scientific base is canonical main 721c03822c421b7f7fcbb2598993b947c4d88419, priority revision 8, refreshed before publication. Consumed PR6144 word is exactly 4f3b67e7c37ae270da9584033132866d0cf63e42; its bytes are exported locally, so cold replay needs no unmerged Git object or network. The source checker is Ali Romman's unchanged main-branch PR5827 local.py. Source and mechanism credit remains with DreamingOfClouds, Ali Romman, Mason Hale, Pierre-Loic Doulcet, JosieElliston and the retained P104/native/controller/framework lineage. Last-read register coalescence is standard; the new result is this literal legal P104 substitution and its complete-word certificate.

Limitations and unrun obligations

No native operator replay, physical caller, compiler, outer ledger, rounded numerical analysis, selected cold replay, Lean or Docker run is included. No new frame pair is introduced, but actual physical placement is not re-certified. The existing caller reserve is not reduced. The five framework assumptions remain. Exact rational substitution does not establish an equal rounded error budget. Independent human and formal proof-kernel review are unclaimed.

Open next questions

  • Can readers 169 and 206 be served by a different legal route that actually removes frame 553 or 1047? Preserve their other meetings and price the complete changed itinerary first.
  • Can the actual caller exploit the 28-field declared inventory? Bind its aliases and lifetime schedule; unchanged peak occupancy alone does not establish a physical memory saving.
  • Does a specified rounded COPY/SCALE implementation admit the substitution with no larger error budget? Bind its numerical and erasure semantics before reuse.

Related open work

CI notes

CI is uncertified. At head 8fbda6f437e5baaf0ded324ec25e6be7e6cb7cc0, run 40725600911 failed plan; replay (research/owned770-descent-pruning) was skipped. The package replay did not run in CI. The onboarding suite ran 678 tests with exactly two failures and 23 skips:

  • test_research_current_status.CurrentStatusTests.test_current_section_matches_selected_record expects the exact **0.003125804** marker in docs/research/current-status.md. Its bold span instead includes the rational equality, so that exact marker is absent.
  • test_research_current_status.CurrentCiNavigationTests.test_current_ci_section_matches_selected_record expects make frontier6030-verify in docs/ci.md, which still describes the Raise conditional kappa to 0.00310045 with independent helper splits #5599 replay and command.

Canonical main 721c03822c421b7f7fcbb2598993b947c4d88419, the PR6030 admission commit bearing [skip ci], changed the selected record without matching these documentation expectations. This package changes neither document nor either test. The failed-job logs for PR #6120 run 40691776027 show the same two assertions and the same failure/skip counts. Open #6050 targets that shared navigation repair. Both failed-job logs were read. A maintainer must re-run CI after main is fixed. Passing local checks are not hosted CI certification.

Merge danger

Door: two-way. Blast radius: package. All changes are isolated in the new research directory; no selected-frontier or shared-code change is requested.

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