> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/how-it-works/decision-traces.md). # Decision Traces: why things happened > **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](/how-it-works/how-the-loop-works.md). 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?" --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aloop.icustomer.ai/how-it-works/decision-traces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.