Historical prototype
Recovery tracks live state, not history depth.
Research-prototype evaluation against Temporal — not the portable TCC Engine shipped today. For current engine evidence, see Research.
0.6–0.9 ms
Prototype TCC recovery · depth 10 → 1,000
61 ms → ~1.7 s
Temporal reconstruction · same workload
In the matched local depth workload, with live continuation state held at ~4 KB, prototype TCC recovery remained approximately history-insensitive across 10–1,000 durable boundaries. Temporal in-flight workflow reconstruction increased with accumulated workflow history.
These are local-harness prototype measurements. They characterize a scaling law. They are not production Cloud latency or portable-engine results.