Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute30Proofs

Route30 minimal-block pushout/determinant provider #

Route29 replaced the two live Section 7 pushout residuals

by one actual central-extension pushout packet assembled from seven split actual K_lambda = K / ker lambda packets.

This route30 sidecar keeps the route29 downstream shape but supplies its actual central-extension packet through MinimalBlockActualCentralExtensionClosers2. Thus a future route swap can use the same semantic family and same-family determinant packet while avoiding the seven route29 split actual central-extension packet axioms. The remaining pushout floor is the narrower self-duality/extraspecial determinant interface used by Closers2.

Route30 provider through the extraspecial actual central-extension closer #

Route30 pushout data.

The single field is the broad actual central-extension pushout packet, but the constructor below obtains it from MinimalBlockActualCentralExtensionClosers2, not from route29's seven split actual central-extension packet axioms.

Instances For

    Route-compatible hooks #

    Construct route30 actual central-extension data through Closers2.

    Residual report: this theorem avoids route29's seven split actual central-extension packet axioms

    • minimalBlock_preheadActualCentralExtensionPhiData;
    • minimalBlock_preheadActualCentralExtensionSquareData;
    • minimalBlock_preheadActualCentralExtensionDiagonalData;
    • minimalBlock_preheadActualCentralExtensionPolarData;
    • minimalBlock_preheadActualCentralExtensionNaturalityData;
    • minimalBlock_preheadActualCentralExtensionAnnihilationData;
    • minimalBlock_preheadActualCentralExtensionRadicalContainmentData.

    Its remaining nonstandard closure is the narrower extraspecial/self-duality floor of MinimalBlockActualCentralExtensionClosers2.

    Route29-compatible split-provider data, but supplied by route30's Closers2 path instead of route29's split packet constructor.

    Route30 supplies the semantic central-pushout residual target from the same actual central-extension family.

    Route30 supplies the live determinant residual target for the same semantic family selected by its actual central-extension packet.

    This is the route-relevant same-family form of the residual; it does not assert the old arbitrary-family axiom.

    Acceptance checks / exact residual report #