Research
Transparent Continuation
Checkpointing.
TCC is the execution architecture behind Trigora. It explores a different approach to durable recovery: preserving resumable execution state rather than reconstructing program position from accumulated history.
TCC eliminates prefix replay when recovering from a committed continuation checkpoint.
Evidence
Recovery scales with live state, not history length.
At fixed ~4 KB live continuation state, TCC recovery remained approximately 0.6–0.9 ms as tested history depth increased from 10 to 1,000.
0.6–0.9 ms
Recovery across tested history depth 10 → 1,000 at ~4 KB live state.
50,000
Generated semantic fuzz cases with zero observed failures in the tested suite.
Controlled evaluation. These measurements characterize scaling behavior, not production-server performance.
Why it matters
History tells you what happened.
A continuation tells you where to continue.
Replay reconstructs the present from retained history. TCC recovers from a committed continuation checkpoint. In the evaluated configuration, recovery cost followed live continuation state rather than retained execution history.
Technical report
Transparent Continuation Checkpointing
The full technical report covers the execution model, recovery semantics, evaluation methodology, healthy-path cost, limitations, and related work.
Benchmarks Detailed experimental results
Limitations Scope and non-claims