Control time,
not state.
$ npm install @tcr-tools/core
State is a snapshot. Bugs live in time.
Debug the past. Fork the future.
State is a snapshot.
Bugs live in time.
Modern applications don’t fail because state is wrong. They fail because time is lost.
Events race. Intents override each other. You see the result — not the path.
TCR models what happened, why it happened, and what else could have happened.
Target Audience
- Teams debugging complex async flows
- High-risk UI (Fintech, Healthcare)
- Deterministic replay requirements
Free to observe.
Paid to understand.
Licensed to prove.
Paid to understand.
Licensed to prove.
<TemporalControlPlane />
Intent
──▶
Resolution
──▶
Timeline
└──▶
Fork
Intent Immutable record of "what was attempted".
Resolution Why it was committed or discarded.
Timeline A traversable history, not just a log.
Fork Explore alternatives safely.
Why did this happen?
- Causality graph
- Supersede / invalidate chains
- Resolution reasons
Included in Pro
What if it didn't?
- Fork from any point
- Parallel timelines
- Side-by-side comparison
Included in Pro
Can I prove it?
- Deterministic replay
- Exportable .tcr files
- Checksums and fingerprints
Advanced License
demo.ts
const timeline = createTimeline()
timeline.action({ type: 'save' })
timeline.undo()
timeline.fork() // create a parallel timeline
Core runtime is free.
Advanced inspection requires a paid license.