Documentation

Q2Presentation.Induction.MinimalBlockPushoutRoute126Closers

Route126 minimal-block pushout/determinant closer #

Route126 currently consumes

whose pushout/determinant frontier is the single broad Section 7 atom

This sidecar leaves the public integrated route files untouched and exports a Route126-named provider with the same downstream determinant-packet shape. It routes through the Route82 central-pushout packets, where the actual square is the extraspecial square attached to one scalar-pushout pairing family and the simple-head proof is split into annihilation on T and descended nonsingularity.

Residual effect for the determinant provider:

The first hook below also reconstructs the old broad actual central-extension packet from those four atoms, for audit purposes, without calling the old broad axiom.

Route126 broad-packet reduction hook #

Reconstruct the current broad actual central-extension pushout packet from the lower Route82 packets.

This is an audit hook: it has the old broad packet conclusion, but its axiom closure is the four concrete Route82 atoms rather than minimalBlock_preheadActualCentralExtensionPushoutData.

Equations
  • One or more equations did not get rendered due to their size.
Instances For

    Route-ready provider #

    Route126 selected semantic family and actual simple-head determinant packet, both projected from the same Route82 scalar-pushout construction.

    Drop-in replacement for MinimalBlockPushoutRoute122Closers.minimalBlock_preheadDeterminantPackets_from_route122.

    It has the same downstream conclusion consumed by the nonterminal Fourier branch, but avoids the broad Route122 central-extension atom and uses the four Route82 Section 7 atoms listed in the module header.

    Current Route126 audit route with only the pushout provider swapped #