Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute34Proofs

Route34 minimal-block pushout/determinant provider #

Route33 uses the route31 provider, whose pushout frontier is the four same-family central-pushout leaves

This sidecar gives a route31-compatible provider from one coherent manuscript packet: the actual scalar central-extension family K_lambda = K / ker lambda. That packet already contains the phi_lambda family, the actual square map, the diagonal and polar identities, naturality, and the simple-head determinant annihilation/radical conclusions. The route34 hook projects those fields back into route31's standard square/polar plus actual determinant interface, so the four route33 residual names disappear from the provider closure.

For coordinators who prefer the finer Section 7 split, this file also exports a route34-named hook through the seven split actual central-extension packets from MinimalBlockActualCentralExtensionPushoutProofs.

Route34 actual central-extension packet #

Route34 data: the actual scalar central-extension pushout family, retained as one coherent manuscript-shaped object and then projected to route31's standard determinant interface.

Instances For

    Route-compatible hooks #

    Construct the route34 coherent actual central-extension packet.

    Residual report: this theorem replaces the four route33 pushout leaves by the single actual central-extension pushout construction minimalBlock_preheadActualCentralExtensionPushoutData.

    The route33 central-pushout leaves, all projected from the same route34 actual central-extension packet. This is an audit hook showing that the quadratic family, square diagonal, polar symmetry, and actual determinant are same-family consequences of one actual pushout object.

    Finer split-packet fallback #

    Route34-named lower provider through the finer seven-packet actual central-extension split.

    This hook is not the main "fewer residuals" route34 provider. It is exported so the supervisor can choose the strictly finer manuscript-shaped frontier if the single coherent actual central-extension packet is considered too broad for the next integration step.

    Acceptance checks / exact residual report #