Recorded, not liveeach trajectory is a fixture
One enginethe playground replays it
Fix, then re-runthe fix is a hop away
Replay a trajectory
A failure worth learning from is recorded once and replayed forever. Each card runs in the playground with its hops, payloads, state and the error explained.
The email that never went outdraft_email → needs-approval → staged → no push subscription. Fix: approve it.10 hops · ends pendingRun it
The job that failed with 401the ticker calls back with a service token the app does not recognise. Fix: one token in both tiers.4 hops · JobRunFailedRun it
The build sent to the wrong planea control-plane capability on the sidecar → 404 by rule. Fix: point the CLI at :3717.3 hops · 404 not_foundRun it
What a replayed failure teaches
Reason · Trace · How to fix
Every error card has the same three parts, and at least one fix is a button. A dead end is a bug in the docs.
Where trajectories come from
The recorder runs the failure on a throwaway control plane and captures the hops; a reviewer writes the three parts. Re-recorded on every forge tag.