Implementation: IMPLEMENTED · Exposure: INTERNAL. See status labels. A cassette is a content-addressed recording of the results a run received from the outside world, so replay can substitute them for live effects.

​
Architecture contract

Pipeline: live run, trace and receipts, cassette, replay, eval, capability evaluation registry, router. A CassetteV1 holds the run and graph identity, the ABI version, its entries and the run receipt hash. Replay reconstructs which node ran, what evidence it saw, what tool resolved, what side effects occurred and why it branched. External effects are replaced by recorded results. Why: replay turns every real run into a regression test and gives the router evidence about which components work.

​
Current implementation

On main, internal only. Cassettes are recorded from a run’s receipt chain; replay runs in recorded-only mode and produces a divergence report; the gate has a replay mode that serves recorded results and denies live execution; and the internal work runtime service accepts POST /v1/replays. None of this is reachable through https://api.allternit.com yet.

​
Availability

​
Developer relevance

Do not depend on replay yet. Do keep effects behind the tool boundary so they can be recorded later.