From ec9c8de2b2a9ce3a005b0cadac56902190cf834a Mon Sep 17 00:00:00 2001 From: RainbowBird Date: Tue, 13 Oct 2026 18:42:11 +0000 Subject: [PATCH] docs(api): name the API step that the exporter waits for Co-Authored-By: Claude Opus 5.5 --- server/docs/ai/adr/2026-10-14-agent-trace.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/docs/ai/adr/2026-10-14-agent-trace.md b/server/docs/ai/adr/2026-10-14-agent-trace.md index f0bfca316a..5665b2fda6 100644 --- a/server/docs/ai/adr/2026-10-14-agent-trace.md +++ b/server/docs/ai/adr/2026-10-14-agent-trace.md @@ -286,7 +286,7 @@ sequenceDiagram 3. Client, in three PRs: 1. Each span takes its own turn as its parent. The turn span carries its IDs and status. The session ID fix. 2. One `LLM request` span for each request, and `Tool execution` spans. - 3. The exporter. Only this part sends data off the device, and it needs step 2 of this list to be deployed. + 3. The exporter. Only this part sends data off the device. It ships after the API of step 2 is deployed. 4. Admin API (`proj-airi/backend`): read runs, spans, and items for one turn, and sort runs across users. 5. Admin dashboard: one timeline for each turn.