Repository navigation
Research: shared-core dirty fan-in with rank-one deviations - #1863
Conversation
|
Batch review at Merged to Reviewed scope: Exact shared-core dirty fan-in identity checked on245 F2 columns and integer fixtures, with rank48 core and three rank1 deviations. The >28 margin is under a declared local tariff charging row gathers as unit operations; no selected source seam, actual recursive/hosting or precision tariff is admitted. 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. |
Result
Adds an exact three-source common-core fan-in with simultaneous rank-one deviations. The source maps are (B_j=B+D_j), with a rank-48 shared core and three distinct rank-one (D_j) on 49 coordinates, so each direct (B_j) map has rank 49.
For arbitrary dirty sources, target, and scratch (t=d), the construction subtracts (Bd), gathers (S=x_1+x_2+x_3) into (t), adds (B(d+S)), restores (t), and applies all three deviations. The arbitrary dirty term cancels exactly. No clean row or source mutation is assumed.
Complete local cost screen
The baseline uses three rank-49 calls and three rank-one dispatch units. The construction uses two rank-48 core calls, three rank-one deviation calls, six rank-one gather/restore calls, and 11 dispatch units. At the selected exponent (a=836330098538459/500000000000000000), with (q=1-a), the difference is
[
3\cdot49^q-2\cdot48^q-17>28.
]
This leaves at most 28 rank-one-equivalent units for additional parent/interface/program costs. The construction requires one 49-coordinate dirty row and up to two guard bits for an integer-valued lift; those charges must fit that budget and the supplier's row stock. The package does not claim that a live supplier seam has been found, does not change the selected profile, and claims no new (\kappa).
Verification
From the repository root:
The direct verifier passes on Python 3.14.7. It checks ranks 48/1/49, all 245 binary basis columns of the arbitrary-dirty five-row interface, an integer-valued fixture, and four negative controls. The package metadata and source pins pass. Python 3.12 is not installed locally, so the registered Python 3.12 replay remains for CI.
Pins and overlap
The task card and SOURCES.json pin base
0b1cccf86e2f5132ed286a26ef0a681a495740ea, selected-record SHA-25610b9e340fd8e354a37a0c4813c90e5de1dd42044b5f6aca4a3fc5a42b685fa32, maintainer review, integration receipt, selected source manifest, and assembly certificate.Nearest work is PR #1531's arbitrary-map DUO, PR #1518's atomic TRIO, PR #1524/Discussion #1579's equal-map common-B connector, and PR #1739's sequential rank-one source update. This construction treats three simultaneous distinct maps with rank-one deviations from a shared core. The final global Discussion refresh stalled in GitHub's GraphQL client; current PR pagination and REST checks of Discussions #1163, #1504, and #1579 found no exact overlap.
Prepared with substantial OpenAI Codex assistance. No predecessor code was imported; no independent human review is claimed.