Series spine, two writer lanes, three AI agents orchestrating in the middle.
0–4s · series spineAcross the top: the series spine. Four articles. Current article highlighted; others queued behind it. The spine is the meta-harness state — the series itself is a chain.
4–10s · two writer lanesTwo lanes drop down from the spine: Vishal’s, Akhil’s. Each lane is a per-author task queue with its own intent-state badge. Lanes carry tasks, not text.
10–14s · orchestration railThe middle column is the orchestration rail. Three AI agents live here: research, adversarial, visual. Pulses light up as each agent fires into one of the lanes.
14–18s · 3 AI agents firingA research agent surfaces a citation into Vishal’s lane. An adversarial agent flags a claim in Akhil’s. A visual agent renders a diagram inline. Agents are deferred, not modal.
18–20s · counter stripA counter strip ticks: words, citations, lessons, sections approved. The numbers are the shared spine state — both writers and all agents push into the same counters.
20–22s · the lanes thesisThe harness arranges the work, not just the chrome. Lanes are first-class — the spine schedules across them, the rail dispatches into them.
what this provesdoclayer is a workstream, not just an editor. Agents and writers share lanes; the spine schedules.