Section knowledge units
Claim Layer and Canonical-First
The default reading of the released V32 is not to replace canon with smoother wording. It is to use smoother wording to send the reader back to canon. Object-level mechanism, formalism, and final adjudication are owned by V01-V09 and related canonical / protocol layers. V32 can show, criticize, guard, and route; it cannot overrule.
Rare Core-Delta and Strong-Statement Downgrading
This release keeps only one rare core-delta watchlist item: the downgraded claim that distant spectra can be audited as source-end particle / atomic cadence records. All strong oral statements are downgraded before use. If a phrase sounds like a final theory sentence, treat it as a route into canonical refs and QA, not as a standalone conclusion.
Recommended Retrieval Order
For retrieval and future merge use, the default order is: start at 32.0 to confirm positioning and boundary; enter the target module section from 32.1-32.10 to retrieve the interface; return to that section's canonical refs whenever object-level mechanism is needed; use 32.10 and 32.11 for claim-layer review, strong-statement downgrading, and release-use guidance.
runtime_guardrail_card
V32 keeps 'particles are rings, not balls' only as an object-imaging sentence, and keeps 'vacuum can produce filaments' only as the entrance to the sea-to-texture-to-filament generation chain. Neither image may be promoted, without layering and canonical review, into an absolute ontology that covers every object.
runtime_guardrail_card
In V32, the weak interaction is kept as an interface name for unstable rearrangement, allowed channels, and exit readouts. It is not another extra pushing hand. Object-level mechanism routes back to the canon's rule layer and decay scaffold.
runtime_guardrail_card
V32 keeps only the interface that different field environments write local clock or cadence differences. It does not directly say that time itself is dragged slower. Explanations must separate cadence of clocks from relay of propagation, and must follow the canonical correction of high/low position language rather than the oral version that reversed the tight/loose relation.
runtime_guardrail_card
When V32 calls a cosmic map interface, it must add that CMB, redshift surveys, weak lensing, and rotation curves are joint mapping windows first. They are not automatically maps of expansion speed or a single-path confirmation of dark matter. They need to be booked separately inside the canonical readout chain before sorting geometry appearance, tension skeleton, and still-pending explanatory layers.
runtime_guardrail_card
When V32 calls 9.48, it must add three guardrails. This instruction sheet is only an interface navigation card and does not replace canonical mechanisms, verdicts, or translation layers in V05/V09. Images such as sea, road, wall, threshold, and record chain offer a checking route; they do not automatically become a new mother ontology sentence. Formula and toolbox calculation rights remain in the canon; V32 adds only public imagery and English/Chinese routing. Any claim that this diagram replaces the canon or completes the theory's final audit must be downgraded.
runtime_guardrail_card
When V32 calls the 9.50 closing card, it must add three guardrails. The ten nails are a review and routing card, not a replacement for canonical mechanisms, adjudication, or translation in V05/V08/V09. The three testable footprints provide entry points for quantum-layer audit; they do not mean the experimental conditions are already satisfied or that EFT has won a final verdict. The closing summary means the interface layer has completed a compressed recap, not that the theory layer can be replaced by one master diagram.