# Schedule > Every member that runs on its own: its card, its wakes on one day, its prompts; how to set a member up on any Claude account. *Source: ยท generated by tools/gen_admin.py from content/admin/, so the page and this file cannot drift. Every page on this site has a .md twin.* --- Every member that runs on its own keeps one card, `content/admin/members//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](https://github.com/SHarness-AI/SHarness-AI__Website/blob/dev/WAKE.md); the brief is [schedules, cards and start pages](../briefs/2026-10-26__brief__schedules-cards-and-start-pages/index.md). 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. ## The cards | Member | Objective | Status | Wakes (London) | Model | Last run | |---|---|---|---|---|---| | [cli](../members/cli/index.md) | 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:00 `CRON_TZ=Europe/London 0 9 * * *` | the session's model | none yet | | [conductor](../members/conductor/index.md) | 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:20 `CRON_TZ=Europe/London 20 7-21/2 * * *` | the session's model (Sonnet would do for the light checks) | 2026-10-26T00:32Z ok | | [dev](../members/dev/index.md) | 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:30 `CRON_TZ=Europe/London 30 9 * * *` | the session's model | 2026-10-26T01:21Z ok | | [pbp](../members/pbp/index.md) | 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:10 `CRON_TZ=Europe/London 10 10 * * *` | the session's model | none yet | | [security](../members/security/index.md) | 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:35 `CRON_TZ=Europe/London 35 21 * * *` | the session's model | none yet | | [sharness.build](../members/sharness.build/index.md) | 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:00 `CRON_TZ=Europe/London 0 9 * * *` | the session's model | none yet | | [sherpa](../members/sherpa/index.md) | 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:45 `CRON_TZ=Europe/London 45 8,17 * * *` | the session's model | none yet | | [website](../members/website/index.md) | 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:15 `CRON_TZ=Europe/London 15 9 * * *` | the session's model | 2026-10-26T01:45Z ok | ## Setting a member up on any Claude account 1. Open the member's page and read its card: the repositories, the session name, the start prompt, the cron, the wake prompt. 2. On the account, start a session with those repositories attached (push access) and name it as the card says. 3. Paste the start prompt. 4. With the editor's go, create one scheduled task on that account from the card's name, cron and wake prompt, firing into that session; the session makes the card active in its next release. 5. A key the role needs is handed sealed, never pasted: https://pki.sgit.ai/handover.md