Workers appear and finish. The graph grows while you watch.
A worker starts and a card for it appears. It finishes, and the card reflects that. A session writes an entry, and the lineage graph gains a node — no refresh, no polling button, because the panels are queries against the running database, not a snapshot taken earlier and shipped to your browser.
Threads and branches populate the same way: open a project with active sessions and you watch structure form instead of reading a finished description of it. The dashboard doesn't summarize what happened after the fact. It shows what's happening.
This is where the other thirteen pages' receipts came from.
Every citation on this hub, the entry numbers in parentheses, points at a row in the same substrate this dashboard queries. There's no separate marketing view built to look better than the product: the panel showing workers and threads here is a live read of the exact data those receipts were pulled from.
That's the difference from a typical product-tour dashboard page. A tour usually shows a screenshot, styled for the pitch, disconnected from anything running. This one is a window onto the database, open right now, rendering rows as they're written.
Reviewed criterion by criterion, not approved on a demo.
The v2 dashboard rebuild went through review before it shipped, and the review approved it with a specific note: “Exceptional work. 14 criteria shipped with evidence, 4 appropriately deferred” (#245). That phrasing means the review checked each acceptance criterion individually against what had actually shipped, rather than approving on the strength of a demo running through a happy path.
Four criteria didn’t ship in that pass. They were deferred and recorded as deferred, not dropped quietly and not faked to pass review (#245).
| What shipped | Detail |
|---|---|
| review outcome | Approved |
| acceptance criteria checked | 14 shipped with evidence, 4 appropriately deferred |
| review method | each criterion checked individually against what shipped, not a demo pass |
| source | Vinculum substrate entry #245 |
Common questions.
Is what I see on the dashboard live data, or a demo?
Live. Every panel runs a query against the running database behind the session doing the work. There's no separate demo mode dressing up sample data to look busier than a real project would (#245).
What does '14 criteria shipped with evidence, 4 appropriately deferred' actually mean?
The review that approved the v2 dashboard checked each acceptance criterion one at a time against what had actually shipped, not against a demo. Fourteen criteria had evidence behind them. Four were deferred on purpose, written down as deferred rather than silently dropped or quietly faked (#245).
Who is the dashboard for?
An operator watching their own fleet of workers: sessions, threads, and the entries they're writing, as they happen. It's the view of your own project, not a public status page or a shared showcase.