Repository navigation
DONE: native lazy tensor boundary #5474
JoyboyBrian
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
DONE — contribution submitted: 5484. Maintainer review remains pending.
Exact head
233828acc3393af4f99e8f3b55ab3095ddf9433c; 2 substantive commits. Local validation and independent agent review are evidence for this scoped contribution, not human or formal-kernel acceptance.The actual lender333 lazy signed-affine boundary now has a uniform all-width bounded-word routing algorithm with O(N) address work and no N-entry routing table, N=512^f. It preserves all four arbitrary caller arrays and saves exactly 2N real writes against the strong materialized comparator. Principal route lanes fall from 36 to 29 and leader comparisons from 34N to 27N. The common paid child and L suffix remain unchanged.
The exact source pins, all-width proof, executable controls and open next questions are in
research/native-lazy-tensor-boundary/. This closes a named source-bound implementation handoff; it does not admit a supplier or change selected κ.Validation: All512 source columns reconstructed; actual dense four-array width1 boundary; independent out-of-place oracle; exhaustive small tensor cycles through width4; eight actual width2 columns; exact route counts; phase/translation/composition/domain controls. Registered Python3.12 normal/optimized checks pass, as do actual on-disk source/receipt/scientific-code rejection controls. Final committed-byte/source-history preflight and official export integrity checks pass. Both normal and optimized direct science pass from a read-only Git-free export with PATH empty; payload hashes are unchanged. Separate AI peer review found no blocking issue.
Limits: Complete setup is fixed and charged, but no actual primitive tariff or total-time crossover is claimed. The exact scalar NEG invoice describes the stated register/sign-reuse RAM schedule, not eagerly evaluated Python operations. Native ownership installation in selected5413, rounded child precision, fixed tapes and supplier/outer admission remain open. No recursive rank, owner-width or kappa change; source f=1 native recipe proof retained as premise.
Prepared by JoyboyBrian with substantial OpenAI Codex assistance; Apache-2.0. All predecessor credit is retained in README/PROOF and exact copied sources. Independent human, formal-kernel, hosted-CI and full selected-supplier verification are unclaimed. Canonical investigation: #5474.
Claim base
32890bc5de034ab8fc93ac88ead7279a6a416d04. Selected frontier unchanged.All reactions