Replay

Reconstruction

Replay does not guess. It reconstructs from explicit inputs: launcher-issued context, workspace state, Reason intelligence, and prior replayable records.

Explicit inputsNormalized replay modelFidelity stays visible

Page Focus

Reconstruction explains how Replay rebuilds a coherent operational story from launcher context, shared state, and product intelligence.

Explicit inputs

Replay depends on valid authority, workspace scope, and a readable product-state surface before it can trust its own reconstruction.

Normalized replay model

Signals are transformed into evidence records, contradiction edges, confidence snapshots, and final outcome states.

Fidelity stays visible

When the story is shallow, Replay should say so clearly rather than pretending it has enough support for a complete conclusion.

Questions This Page Answers

What data does Replay require before it reconstructs a story?
How does limited evidence affect the replay window?
When should operators trust or question the reconstructed sequence?

Continue Reading

Move across the shared CTK documentation model.