Continuations

A TCC continuation is the logical state required to resume a Program at a durable boundary: control position, destination-live values, and the identity of the artifact that compiled to that point.

It is not:

• the process heap
• a snapshot of process memory
• a snapshot of WASM linear memory

The host stores that logical state. Another process can load it and continue. The original process can be gone.

Values that are still live at the boundary are part of the continuation. Values that are dead are not a history log the engine replays. Effect outcomes that already committed are reused by identity, not by running the effect function again. See Effect identity.

The technical report is the longer argument: Transparent Continuation Checkpointing.