One night of agentic design, replayed from its timestamps.
Computed in the browser from one JSON file. Times are UTC. Peer times are message-arrival times in the design session, not the peer's own working time.
01 / Replay
Who did what, when.
One lane per participant. Colour is the protocol the work belonged to. Press play or drag the scrubber: the lanes fill in as the night advances, and the composition graph in section 06 lights up as each protocol gets its first case.
Swimlanes
Design-session bars are question → decision; orchestrator slivers are relay → draft arrived. The pull-request lane runs from opened to merged.
Table view
02 / Concurrency
How many agent participants had a recorded episode running at each second: the two sessions and the sub-agents. The operator and the pull requests are shown as separate strips on the same time axis, not added in.
Agents active at once
Table view
03 / Where the time went
Each participant's observed span, split by kind of time. Sub-agents are counted from their first launch to their last report; the others across the whole window. Where two kinds overlap in one lane, repair beats deciding beats working beats waiting.
All agent lanes together
Per participant
Bars are part-to-whole of each lane's own span, ordered by kind, not by clock time.
Table view
04 / Decision anatomy
The hand-off takes seconds. The record waits.
design.decision/1, step by step
Left: question to draft arrived, on a 0–20 minute scale. Right: draft arrived to the record's pull request opening, on its own scale. The ▲ marks the operator's commit word where this record has it.
Table view
Cadence: time between consecutive decisions
Table view
05 / What if
Four protocol changes, priced on this night.
The four changes proposed in the process-timings note, section 5. Each switch recomputes its estimate from the data and redraws sections 01–04. Model estimate marks every number here: it is what the recorded timestamps imply under a stated assumption, not a measurement of a night that happened.
The four estimates measure different clocks: record latency summed per record, decision latency, agent working time, and repair time. Adding them would count overlapping wall-clock time more than once.
06 / Composition
The composition behind it.
Triggers open protocols; protocols are taken by agents and principals; agents act through capabilities; capabilities bind to connections. Hover or focus a node to trace everything upstream and downstream of it. During the replay, a node is lit once a protocol that reaches it has had its first case.
Triggers → protocols → agents → capabilities → connections
Table view
07 / Method
Where every number comes from.
Nothing on this page is typed in by hand. Each figure is computed when the page loads, from the data file and the definitions below.