Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute21Proofs

Route21 minimal-block actual central-extension pushout sidecar #

Route20 exposes the Section 7 pushout/determinant step through the single broad residual

The older split-packet API in MinimalBlockActualCentralExtensionPushoutProofs already separates that manuscript construction into the same-family pieces used in the paper:

This sidecar gives route21-named hooks for later integration. It reassembles the route20-facing lower pushout packet from those strictly finer residuals and does not use minimalBlock_preheadActualCentralExtensionPushoutData.

Route21 split actual-pushout packet #

Route21 actual central-extension data, stored as split manuscript-shaped packets rather than as the broad route20 residual.

All fields are tied to the same phi_lambda/q_lambda family, so the projected route packet uses one coherent scalar central-extension pushout construction.

Instances For

    Route20-shaped determinant wrapper projected from the route21 split data. This lets the new hook reuse the already verified route20 projection code.

    Equations
    Instances For

      Assembly and route-compatible hooks #

      Assemble route21 data from the split actual central-extension packets.

      The nonstandard closure of this theorem is the seven split residuals from MinimalBlockActualCentralExtensionPushoutProofs, not the route20 broad packet.

      Broad actual central-extension packet recovered from route21 split packets. This theorem exists for audits; the integration hook below consumes the lower route packet directly.

      Route21 replacement for minimalBlock_preheadPushoutRouteLowerData_from_route20ActualDeterminant.

      It has the same conclusion as the route20 hook, but replaces route20's broad actual-pushout residual by the finer split central-extension packets.

      Acceptance checks / residual report #