Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute35Proofs

Route35 minimal-block pushout/determinant provider #

Route34's pushout branch still depends on the broad residual minimalBlock_preheadActualCentralExtensionPushoutData.

This sidecar keeps the route34-facing conclusion, but obtains the actual central-extension packet from the existing extraspecial/self-duality closers in MinimalBlockActualCentralExtensionClosers2. Consequently the route35 lower provider has no dependency on the broad route34 residual and no dependency on the seven split actual-central-extension residuals; its remaining closure is the more explicit extraspecial/self-duality determinant floor.

Route35 actual central-extension packet #

Route35 data: the actual central-extension pushout packet, supplied through the existing extraspecial/self-duality closer rather than through the broad route34 axiom.

Instances For

    Route35 data projected to the lower pushout route consumed by the integrated nonterminal branch.

    Equations
    Instances For

      Route-compatible hooks #

      Construct route35 actual central-extension data from the existing extraspecial/self-duality closers.

      Residual report: this theorem avoids minimalBlock_preheadActualCentralExtensionPushoutData and the seven split actual-central-extension packet axioms. Its remaining nonstandard closure is the explicit extraspecial/self-duality floor exposed by MinimalBlockActualCentralExtensionClosers2.

      Broad actual central-extension packet recovered through route35.

      This is exported as an audit hook: the conclusion matches the route34 residual, but the proof does not call the route34 broad residual axiom.

      Acceptance checks / exact residual report #