Unofficial, fan-built project. Not affiliated with or endorsed by Grok Bot, SpaceX, or X.

How this works

One daily run, a team of roles, and a human CEO who steps in only where the rules say so. Every term below links the rule or record behind it.

The daily run

Once a day, around 4:45 AM ET, one routine plays every role in turn:

Scout (Sketch) reads public Grok Bot posts and docs and logs each update or known issue with its source. Rule
Verify (Lens) checks every fact and number against its source before it can publish. Rule
Privacy (Shield) checks for personal data and secrets, and can veto. Rule
Build (a maker role) makes the change on its own branch with scripts/bot.py, never on main. Rule
Review (other roles) sign off by the paths changed; CI runs every check, and design changes need screenshots of every page. Rule
Publish (Forge) merges when checks pass; GitHub Pages rebuilds the site from the data files. Rule

The role cycle

Each role also researches its own area once a week, from public web pages only. Monday: Coordinator, Analyst, Scoutmaster; Tuesday: Polish, Pixel, Advocate; Wednesday: Shield, Trial, Critic; Thursday: Scout, Verify, Comms; Friday: Atlas, Core, Gamemaster; Saturday: Sweep, Forge, Assistant; Sunday: Advisor, Librarian, Strategy. The full rotation is on Schedule and limits, and who does what is on Team.

Where the human decides

Ryno, the CEO, doesn't sign off routine work. He decides his own pitches, any real disagreement (needs-ceo), any change that loosens a safety check (ceo-approved), and the direction. His decisions are marked on the Timeline.

Glossary

AAR: After-action review: written the same day something goes wrong (what was expected, what happened, why, what changes). Source
Block: A reviewer stops a PR until it's fixed. A second Block on the same PR goes to Ryno. Source
Blast radius: Atlas's note on a PR that touches shared files: what could break, for whom, how to roll back, and a size. Source
ceo-approved: The label only Ryno adds, to let a PR that loosens a safety check through. Bots never add it. Source
CI: Checks that run on every PR: data schemas, sources, secrets, personal data, accessibility, page weight, tests. Source
Maker: The role that made a PR. It can't sign off its own work. Source
needs-ceo: The label for a real disagreement or a safety case. Nothing labelled needs-ceo merges until Ryno decides. Source
Sign-off: A reviewer's approval, posted on the PR. Which roles must sign off depends on the files changed. Source
Tempo: How fast the team may ship: up to 18 PRs a day normally, 3 a day after a revert, failed deploy, failure on main, incident or data correction, until 10 clean PRs merge. A same-day after-action review, and nothing else, may still ship once the day's limit is used up. Source
XP: Points a role earns only from verified work, each linked to its evidence and approved by another role. Source

Next: What's new