Skip to content

Conditional kappa = 0.001296606691405309: response-kernel cancellation and nested-donor flags on R715 - #483

Closed
Dugongue wants to merge 4 commits into
CrocSwap:mainfrom
Dugongue:tn12
Closed

Dugongue wants to merge 4 commits into
CrocSwap:mainfrom
Dugongue:tn12

Conversation

@Dugongue

Copy link
Copy Markdown
Contributor

This adds research/tensor-response-r715/, a source-bound offline construction and replay package.

Conditional kappa = 0.001296606691405309, exactly 1296606691405309/1000000000000000000: +0.08476450% over #478 (0.001295508560071773) and +0.19840410% over the pinned warm #473 claim (0.001294039264416565). The bit supplier binds. This compares the complete whole-owner route; it is not a claim to exceed proposals using different admission assumptions.

Concrete new mechanisms

  1. Simultaneous response-kernel cancellation. Compute each immutable-source injection's transported target response. Delete a packet only when its response sum vanishes for every source. The useful cross-helper pair reads source3 at helpers444 and246; neither injection is removable alone. Rebuild inverse cleanup. Its local paid delta replaces rank1 plus rank5 by rank6, so strict subadditivity gives a moment improvement for every relevant exponent. Ten further duplicate pairs only reduce scalar work. Altogether22 injections and22 cleanup additions disappear, with all22 single-deletion controls rejected.
  2. Nested-donor flags. Replace the old one-entrance-per-donor construction restriction with an explicit sufficient flag schedule. Donors receive logical shears at increasing nested frames; all dirty values remain arbitrary. Ten pivot upgrades yield110 pivots,102 physical donors,120 correction groups and total entrance rank129. Exact response relations, frame chains and residual isometries are checked. The new constructor is explicit; the old constructor's equal-entrance guard is not silently ignored.

These are combined with the new retain-and-repair #473 kernel and our14 target factors from #478. Gains are priced through the complete composed program, never added. The full local/native and physical ownership checks use the actual changed word. All88 calls use one uniform provider; all62920 residual occurrences remain wholly on single physical families. No unverified heterogeneous portfolio or cross-family split contributes.

Exact pricing and validation

  • Bit saving lower bound: 1298290062988365072981/1000000000000000000000000.
  • Complex saving lower bound: 1305231506267591/1000000000000000000, the unchanged source-bound completed supplier from Conditional kappa = 0.001274548075945587: full-nine-axis kernel normalization and same-owner spectator borrowing #471.
  • Bit dimension78,9600 live/9609 physical families; complete rank mass745536.
  • Fresh physical prefix837bits, charged896; three-level coefficient2567bits, charged2624; row coefficient19431<20161.
  • Source reconstruction,955 arbitrary-dirty binary columns, rational frames/integer operand spans, native signed/formal columns, physical target labels, mixing controls, Gram/projectors, global owner audit, fresh invoice, both exact moment implementations and all47 strict outer inequalities pass. Mutation controls cover the changed constructors and inherited physical audit.

Run:

python -B research/tensor-response-r715/verify.py /absolute/new/output

Python3.11+, SymPy, a C++17 compiler and Boost headers are required. Replay uses no network or optimizer. Default replay rebuilds both suppliers. Our completed changed-component run explicitly reuses the unchanged complex supplier only after matching87 implementation hashes and17 output hashes against its pinned completed receipt. That mode emits a distinct receipt; it is not described as a fresh complex execution. VALIDATION.json records the actual run scope. GitHub CI is separate and is not claimed passed.

Sources, credit and retained research

Direct inputs: #473 (new warm kernel), #478 (retained14 target factors), #472/#470/#467 (R715 kernels, retiming, whole-owner pooling), #463 (R715 carrier and XOR word), #450 (target mixing), #455/#476 (earlier target factoring and portable audits), and #471 (unchanged complex normalization/spectators). The retained complex/hosting/compiler lineage includes #449, #456, #457, #451, #454, #417, #442, #433, #425, #386, #377 and #370; outer assembly comes through #434/#315. #469 is credited for delivery scheduling, not its separate cross-family proposal. Upstream notices and licenses are preserved.

#477's categorized experiment archive helped avoid repeating exhausted representations. #475, #474 and #397 were reviewed without counting their distinct results as numerical gains; #461/#465's sharper bad-edge charge is not used. RECENT-PRS.json records the frozen source sweep through #478 and explicitly records unavailable historical receipt files at the pinned #473 head.

The library search read actual proof sources: ReasBook Woodbury/Schur update structure, Mathlib matroid exchange and subspace flags, OpenAI annihilator and SL-commutator proofs, CSLib diamond/confluence, Hadamard6 and prior tensor/CNOT project lemmas. Source hashes and sufficient mathematical proofs are retained. No new Lean kernel certification or exhaustive literature-priority claim is made.

The third search lane tested noncommuting transport, GL3 basis changes, chronological affine synthesis, central-response cancellation and cleanup resynthesis. It found no admissible gain. These constructions, bounded results and C++ sources are retained for future workers; they are not advertised as a third successful technique. Previous affine-controller and heterogeneous-provider notes remain explicitly uninstantiated or unverified.

Scope

All inherited all-size supplier/compiler, mutable-basis/target-label, complete-call correlated-dirty hosting, compressed-window, restored-work, precision, row and analytic interfaces remain conditional. This is not an unconditional sub-n-log-n multiplication theorem, a new Lean certificate, or a global optimum.

@Mister-Meeseeks

Copy link
Copy Markdown
Contributor

Thank you @Dugongue. This contribution is now retained on main in the scoped 100-PR review and contributor credits.

Contribution: Response-kernel cancellation and nested donor flags.

Review and limits: The new flag schedule is an explicit extension, not a silently relaxed equal-entrance guard. Full dirty responses and shared transition costs are charged.

The complete original source, notices and relevant execution evidence are retained through the pinned source archive. The review distinguishes fresh local runs, source-bound historical Linux CI and prior exact-head review; it does not claim 100 fresh full mathematical audits. Closing this historical PR as reconciled. This preserves parallel and cumulative credit without replacing the selected frontier or promoting priced research targets to completed constructions.

Reviewed head: 3738c3ce2d04d6a6c6363408ff9402286f592bc7. Publication: 7f19399def7c51ff8016d9190999830ef3e17f95.

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