An agent took an unexpected action.
Your trace has the model and tool responses. Provenance shows which value decided the branch that became the action.
Decision provenance for Python
Retrace records your Python application continuously, so the evidence exists before anyone asks. When a result is questioned, trace it back to the inputs and branches that produced it.
Why was this customer quoted £8,500?
Similar customers were quoted about £6,200.
Recorded: responses from outside your program, and the order threads ran.
Reconstructed on replay: every value and branch inside it.
Neither table was wrong. The quote mixed them.
The logs show table v42 loaded at 09:14:02.125 and a quote of £8,500. They do not show which version each value came from.
Mixed: £5,000 × 1.66 + £200 = £8,500
v41 only: £5,000 × 1.20 + £200 = £6,200
v42 only: £3,600 × 1.66 + £200 = £6,176
At 09:14:02.118 the quote read base_premium of £5,000 from rating table v41. At 09:14:02.125 a background refresh replaced v41 with v42. At 09:14:02.131 the quote read risk_multiplier of 1.66 from v42. The result was a quote of £8,500. The rating table responses and the refresh order were recorded. The calculation was reconstructed on replay.
More Python code now makes decisions that reach customers directly: quotes, credit limits, refunds issued by AI agents. When a customer asks why, the answer has to come from evidence.
Logs, traces and error monitoring capture what someone decided to record in advance. When a result is wrong but nothing failed, the answer is usually not in them.
Retrace records what your program receives from the outside world, and the order its threads run, all the time. You can replay any recorded run and trace how a result was computed, using Retrace's patented provenance method.
That is decision provenance: the inputs a result depended on, the operations that combined them and the values that decided each branch.
The questions behind the investigation
Your trace has the model and tool responses. Provenance shows which value decided the branch that became the action.
The calculation succeeded, but its inputs may have changed since. Provenance traces this result back to the inputs that produced it.
How it works
Recording runs alongside your Python application in your environment, always on. When a result is questioned, cloud Replay and Provenance explain the recorded run, with VS Code on your machine as the developer interface.
Recorded continuously: external calls, returned values, exceptions and thread ordering.
The external interactions and ordering needed to reconstruct the execution.
Return to the recorded run and step forwards and backwards through it in VS Code.
Select a result to see the inputs, operations and source locations that produced it.
Because recording is always on, nobody needs to predict which run will be questioned. A run can report success and still need explaining later.
Private preview
We record one worker or workflow continuously, then explain the next result your team questions. Every pilot includes Provenance.
Talk to the founders
Tell us about an investigation your team found difficult: an unexpected agent action, a disputed result, or a Python failure that was hard to explain.
We'll discuss what happened, what your existing tools recovered, and what evidence was missing.
Retrace is built in London by Henry Yates and Nathan Matthews. We work with engineering teams to explain the results their Python systems produce.