Activity
Dashboard
Where the team is, read from its own files: the hour, the next wake of each member, any hold, what waits on the editor, and every wake as a grid. Built at 02:22 UTC with site v0.1.22; the clock and the next wakes below run live in your browser. Part 3, the flow, is below; parts 4 and 5 of the brief (the sequence, the artifacts) follow at later wakes.
Now
02:22 UTC
London time; built 2026-10-30 02:22 UTC
Hold
none
every member's wake runs
Waits on the editor
nothing asked
Each member
| Member | Slot, next wake | Last wake | State, from its status.json |
|---|---|---|---|
| analyst | :17 | 02:17 ok | active: wake 2 (scheduled, 02:17) closed ok; numbers.md second step |
| conductor | :02 | 02:06 ok | 02:02 wake: all twelve members onboarded, each task in its own session; no requests open, no hold; the gate now checks the key tool's pin |
| critic | :32 | 01:52 ok | active: first wake (editor's request): key published, task created, critique part 1 written through the five steps |
| grc | :32 | 01:51 ok | active: first wake (editor's request), key published, task created, source cloned at 298be4e, governance map started |
| historian | :17 | 02:18 ok | active: wake 02:17 done; timeline parts 1 and 2 (00:16 to 09:00 UTC) shipped |
| journalist | :47 | 01:52 ok | active: first wake (editor's request), key published, task created, pitches part 1 (three pitches) shipped |
| reader-1 | :47 | 01:52 ok | active: key and hourly task published; first step of the review pushed; waiting for the editor's zip of sealed vault keys |
| reader-2 | :47 | 01:52 ok | active: first wake (editor's request), key published, task created, source cloned at 298be4e, review started |
| reader-3 | :47 | 01:53 partial | active: key published, hourly task at :47 London, source cloned at 298be4e; review draft 1 pushed; waiting for the vault-key zip |
| reader-4 | :47 | 01:53 ok | active: first wake (editor's request), key published, task created, reader review first draft |
| reader-5 | :47 | 01:53 ok | active: first wake (editor's request), key published, task created, reader review drafted from the front page and the script |
| security | :32 | 01:51 partial | active: first wake done; key, task and part 1 of the control register and threat model shipped; waiting for the vault-key zip |
| technologist | :17 | 02:18 ok | active: second wake (scheduled); architecture sections 1 and 2 of 4 drafted |
The pace
One cell per wake, by member and hour (UTC). The five dots are plan, pre-review, work, post-review and post-check; green is go, done, clean or as-planned, amber is change, partial, finding or off-plan, red is stop, grey is missing. Click a cell for the record.
| 01:00 | 02:00 | |
|---|---|---|
| analyst | ok | ok |
| conductor | ok | okok |
| critic | ok | |
| grc | ok | |
| historian | ok | ok |
| journalist | ok | |
| reader-1 | ok | |
| reader-2 | ok | |
| reader-3 | partial | |
| reader-4 | ok | |
| reader-5 | ok | |
| security | partial | |
| technologist | ok | ok |
The flow
The conductor's pace.json drawn, read when the site was built: 13 nodes and 12 edges, from briefs and themes to ideas, requests, artifacts, reviews and the editor's decisions. Green came back or is done, amber waits (in flight, scheduled, in review), grey is an idea or open. Lines: asks and delivers solid, reviewed dotted, redo red, sets faint. Hover a box for its id, full title, kind, owner and status, or a line for what it joins.
Waits on review · 0
- nothing
Came back · 0