request.accepted
Input, product context, environment, and user state enter the trace envelope.
Observe / execution evidence
Every branch, one trace.
Inspect trace ↓
Understand a workflow as the system experienced it: messages, retrieval, tools, routing, retries, policy decisions, evaluations, and outcome context in sequence.
Trace / 8F2A
The execution is the unit of debugging.
Spans05
00request.accepted
01policy.resolved
02route.selected
03tool.authorized
04output.evaluated
TimelineTrace data
policy.resolved
Identity, region, tool scope, and response constraints resolve before routing.
route.selected
Candidate B is selected from the active pool using the current decision policy.
tool.authorized
The refund lookup remains within the approved action boundary.
output.evaluated
Deterministic checks and an application-defined quality signal attach to the final span.
What the trace keeps together
Branch-aware.
Parent and child spans preserve retries, fallbacks, parallel tools, and evaluation branches.
Outcome-aware.
Application metadata and user outcomes sit beside model and tool activity instead of in another system.
Stack-aware.
A stable trace model can feed the logs, metrics, and review workflows an engineering team already operates.
From evidence to action