Time Travel Studio

Time Travel Studio is the hero visualization — the capability no other planning system has. Replay any past commit. See whether its resilience score and break-day projection were correct. Inspect the counterfactual: what would have happened if the alternative posture had been chosen.

A past commit gets selected — a PO release decision from three weeks ago, scored at 78% resilience with a break-day projection at Day 9. The Studio replays the three weeks. The realized events arrive day by day on the timeline: a supplier slip on Day 4, a customer pull-in on Day 6, an FX shift on Day 8. The committed plan absorbs each one or breaks. The break-day projection from three weeks ago is overlaid against what actually happened. In this case, the break occurred on Day 11 — two days later than projected.

The discrepancy is itself learning material. Why was the projection two days early? The Studio shows the iteration cluster that predicted Day 9 didn't sample the customer pull-in that actually happened; the realized pull-in delayed the break by absorbing demand that would otherwise have compounded the supplier slip's impact. The Risk Library updates: this combination is now better understood. Next quarter's predictions get sharper.

Counterfactual replay is the policy-discussion artifact. Same period, alternative posture: the 4-day-safety scope variant would have absorbed the same events without breaking — but at a $640K higher carrying cost over the period. The trade-off is visible in dollars. The CSCO reviews the past quarter's commits in the Studio. Which held, which broke, which broke earlier or later than projected. The lessons become policy adjustments. The board presentation cites specific Studio replays as evidence.

↓ Full MIC worked-example replay with named numbers — the specific iteration cluster behind the Day-9 projection, the per-day event stream, the counterfactual posture's dollar figures — unlocks at gate 3.