Module replay 

Historical reproduction from a replay bundle (spec 004, 3.3).

Scope first, before any byte is resolved; then capture completeness, lifetimes, bounds, integrity and every cross-reference; then the plan is loaded with its retained dependencies and the pure core is driven with the retained snapshot, the recorded evaluation time and the retained values in actual supply order. reproduced means the record-canonical judgment bytes equal the retained run record’s; a valid, complete replay with other bytes is diverged; anything else is incomparable with a typed reason and location. No backend is called: there is none here.

Nothing digests the bundle’s own scope field: relabeling is caught because every supply’s request identity is recomputed under the claimed scope. A bundle with no supplies has no identity to contradict a relabeled scope; a bundle is evidence of what the host retained, never an attestation (spec 004, 3.1.1).

Structs

ReplayConfig

The caller’s trusted replay configuration.

Reproduced

A case whose judgment reproduced byte for byte, with what candidate comparison needs. Historical timing, attempts and cost stay in the run record: copied observations, never remeasured. Only reproduce constructs one, so a candidate is only ever compared on a reproduced case (spec 004, 3.4.4).

RetainedSupply

One checked supply entry.

Enums

Incomparable

Why a case cannot be reproduced or compared.

Inconsistency

A cross-reference that does not hold.

ReplayOutcome

RetainedValue

A retained value, as reproduction supplied it.

Functions

reproduce

Reproduce one retained decision.