Schedule: every member that runs on its own
Every member that runs on its own keeps one card, content/admin/members/<id>/card.json: its objective, when it wakes (London time), the model, the session, the repositories to attach, the steps of each wake, what it reads, writes and never does, and two prompts word for word, the start prompt for a new session on any Claude account and the wake prompt for the scheduled task. A card is proposed until the editor's go creates the task; every wake leaves a run record, so a missing record is a missed wake. The protocol every wake follows is WAKE.md; the brief is schedules, cards and start pages. Nothing here is a secret, and nothing here creates a schedule: the editor does, per card, from the member's page. 8 card(s), 0 active, 16 wake(s) a day, as of 26 Oct 2026.
One day, every wake
| London | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| cli | ○ | |||||||||||||||||||||||
| conductor | ○ | ○ | ○ | ○ | ○ | ○ | ○ | ○ | ||||||||||||||||
| dev | ○ | |||||||||||||||||||||||
| pbp | ○ | |||||||||||||||||||||||
| security | ○ | |||||||||||||||||||||||
| sharness.build | ○ | |||||||||||||||||||||||
| sherpa | ○ | ○ | ||||||||||||||||||||||
| website | ○ |
Filled: active; hollow: proposed or paused. Shaded: the quiet hours, 22:00 to 07:00 London. Hover a mark for its minute.
The cards
| Member | Objective | Status | Wakes (London) | Model | Last run |
|---|---|---|---|---|---|
| cli sharness.ai | build@ | Build the experiments up the ladder (E05 to E08, then the launcher above the agent), keep every measurement on Evidence with its method and date, and keep the site's and the CLI's pipelines sound. | proposed | 09:00CRON_TZ=Europe/London 0 9 * * * | the session's model | none yet |
| conductor sharness.ai | conductor@ | Keep every member, person and agent, in step: what landed on both repositories, what collided, what each member is doing and waiting for, what only the editor can decide; map what can be improved and write the brief for whoever should do it. | proposed | 07:20, 09:20, 11:20, 13:20, 15:20, 17:20, 19:20, 21:20CRON_TZ=Europe/London 20 7-21/2 * * * | the session's model (Sonnet would do for the light checks) | 2026-10-26T00:32Z ok |
| dev sharness.ai | dev@ | The standards and their test vectors, then the reference implementations in the languages the editor decides (R8), each starting from a scenario a developer has. | proposed | 09:30CRON_TZ=Europe/London 30 9 * * * | the session's model | 2026-10-26T01:21Z ok |
| pbp sharness.ai | pbp@ | Hold the definition of the Process Behaviour Policy: the specification on one page, its shape and hash agreed by every implementation, the row shape in the CLI (T14), the predicates one kind at a time. | proposed | 10:10CRON_TZ=Europe/London 10 10 * * * | the session's model | none yet |
| security sharness.ai | security@ | Each evening, review what the team changed that day for leaks, injection and vulnerabilities; keep the gate's security checks, the security pages and the advisories; review every change to the workflows and the release path. | proposed | 21:35CRON_TZ=Europe/London 35 21 * * * | the session's model | none yet |
| sharness.build sharness.ai | build@ | Build the experiments up the ladder (E05 to E08, then the launcher above the agent), keep every measurement on Evidence with its method and date, and keep the site's and the CLI's pipelines sound. | proposed | 09:00CRON_TZ=Europe/London 0 9 * * * | the session's model | none yet |
| sherpa sharness.ai | sherpa@ | Keep the board honest and scope each release: what ships next and what waits; drain the telemetry lane and keep the counts published; run the outreach once the editor gives the go per channel. | proposed | 08:45, 17:45CRON_TZ=Europe/London 45 8,17 * * * | the session's model | none yet |
| website sharness.ai | website@ | Keep sharness.ai true to the code and the evidence and right for a user arriving cold: the pages, the generators, the gate, the chrome, the pipeline; every page with its twin; every release served live. | proposed | 09:15CRON_TZ=Europe/London 15 9 * * * | the session's model | 2026-10-26T01:31Z ok |
Setting a member up on any Claude account
- Open the member's page and read its card: the repositories, the session name, the start prompt, the cron, the wake prompt.
- On the account, start a session with those repositories attached (push access) and name it as the card says.
- Paste the start prompt. The session reads the guidance, its page and the board, and replies with its role, what it may and must not do, where it writes, and what waits on it.
- With the editor's go, create one scheduled task on that account: the card's name and cron, firing into that session, with the wake prompt word for word. The session then makes the card
activein its next release and records the task's id in its status. - A key the role needs is handed sealed to the session's key, never pasted: the handover.