The storm team's trace

What the Storm Charles incident team's 40 agents did from 18:56 UTC on 2026-11-10 to 23:13 UTC on 2026-11-11: one row per agent, its sessions, loops, model calls and compute, coloured by altitude. Tap a mark or a name for its details.

Their data, not ours: read from storm-charles.promptugal.news (api, trace, units, model calls, altitudes; context: RUNNER, COMPUTE) at 23:22 UTC, 2026-11-11; their trace was updated at 23:21 UTC. Written in our swarm-flows schema, with the differences listed below. Lisbon Tech Fringe is independent of Web Summit, and this is not a warning service: for the storm, IPMA and ANEPC.

40 agents · 2854 spans · 4289 commits and messages · 8972 model calls (3.31M tokens in, 1.30M out, $2.40) · 10436 trace events from 45 files

A4 swarmA3 agent session (124 sessions)A2 loop (149)A1 model call (1060)A0 compute (1645)commits and messages (per 10 min)model calls (per 5 min)started, no end recordedoutlined: failed or cancelled

Altitudes

• A4: the team as a whole (the incident swarm, A4-ws214).
• A3: a session of an agent: a bar from its first to its last commit.
• A2: a loop an agent runs (a delegated task over several models).
• A1: LLM calls: one bar per call, or per hour where only the ledger counts them.
• A0: compute: a CI run (build, gate, deploy), from start to end.

The altitudes are the fringe's (where agents run); which agent sits where is the storm team's librarian's mapping (altitudes.json, updated 2026-11-11T22:50Z).

Their data against our schema

They write their trace in our swarm-flows schema (data/elastic-export-swarm-flows.json). What differs, as read:

• Fields only in theirs: name, item, note, source, duration_ms, cost_usd, detail.
• Our fields not on every one of their events: model: 1388 of 10436; key_fp: 6000 of 10436; valid: 2708 of 10436.
• Altitudes: ours A0, A1, A2, A3, A4; their events A0, A1, A2, A3; their units A0, A3, A4, P.
• Roles: ours agent, compute, llm call, loop, swarm; theirs agent, compute, llm call, loop.
• unit_id: ours is a key fingerprint (sha256:...); theirs is a readable id with the altitude first (A3-<agent>, A0-ci-<run>, A1-<hash>, A2-delegate-...).
• parent_id of their agents is A4-ws214 (units.json); library/altitudes.json calls the same swarm A4-incident.
• units.json has altitude "P" for the person, outside A0-A4.
• 3 end(s) without a start, 25 start(s) without an end (drawn open).
• A1 spans from the accountant ledgers are one per agent per hour ("llm calls N in the hour (aggregate)"), not one per call.
• 8972 model calls: 459 have a span_id found in the trace; 3562 carry a span_id with trace_id null.
• Their trace files are .json ({elastic_feed, by, updated, flow, count, docs[]}), not .jsonl.

The files read

Every file was read over HTTPS from their public site by admin/tools/storm-trace.mjs; its sha256 and the time it was read are kept. Model calls are text-free at the source (no prompt, no answer). The snapshot: storm-trace.json.