For the complete documentation index, see llms.txt. This page is also available as Markdown.

Decision Traces: why things happened

Every action records why it happened — inputs, score, decision, and the outcome it is tied to.

Availability: viewing the full reasoning behind every action is on Team and Enterprise.

A Decision Trace is the receipt for everything the system does. For any action it records what it saw, the FIRE score and signals, the decision it made and why, the channel it activated, and the outcome that followed — all tied together by the same trace ID that runs through the loop.

That's what makes measurement honest: because the click, the decision, and the closed deal share one trace ID, you can follow any result back to the exact reasoning that caused it. No black box — and no tool grading its own homework.

Open a trace any time you want to ask "why did we do that?"

Last updated