Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute40Proofs

Route40 minimal-block pushout/determinant provider #

Route39's Section 7 pushout provider replaces the old bundled residuals by the seven actual central-extension packet leaves:

This Route40 sidecar keeps Route39's downstream shape, but obtains the broad actual central-extension packet from MinimalBlockExtraspecialClosers3. That closer reassembles the actual K_lambda = K / ker lambda pushout data from the manuscript-shaped square/polar construction and the same-family prop:simpleheaddet determinant packet (manuscript §7.1, Proposition 7.4, with the determinant background from §6).

Thus the provider below is drop-in compatible with Route39 while removing all seven Route39 split actual-central-extension residual names from its axiom closure. No new axiom is introduced here.

Route40 packet #

Route40 data: the broad actual central-extension pushout packet, supplied by the coherent extraspecial closer rather than Route39's seven split packet axioms.

Instances For

    Route40 projected to the Route39 provider structure.

    Equations
    Instances For

      Route-compatible hooks #

      Construct Route40 data through the coherent extraspecial central-extension closer.

      Residual report: the axiom closure of this theorem avoids all seven Route39 split actual-central-extension packet names. Its remaining pushout frontier is the MinimalBlockExtraspecialClosers3 floor:

      • minimalBlock_preheadCentralPushoutSquarePolarData;
      • minimalBlock_preheadCentralPushoutSimpleHeadDeterminantActualData.

      Audit hook: Route40 recovers the broad actual central-extension packet without using the seven Route39 split packet axioms.

      Acceptance checks / exact residual report #