Decision Log

Problem

An action-only log can tell the reviewer that the agent shorted a position at 14:32, but not which signals it weighed or which alternatives it rejected. Debugging a wrong action degenerates into guessing what the model might have been thinking, and user-facing explanations become impossible to provide truthfully. The team is forced to choose between piecing the reasoning back together from incomplete clues or accepting that some agent decisions are simply unexplainable after the fact.

Solution

Persist reasoning at a chosen granularity (full trace, key decisions, or summary). Link each action in the provenance ledger to its trace. Indexed by request id and time for retrieval.

When to use

• Action-only logs leave you unable to explain why the agent did something.
• Reasoning at some granularity (full trace, key decisions, summary) can be captured and stored cheaply.
• Post-hoc review or debugging routinely needs to consult the reasoning chain.