Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run

Most people open Grok Bot, type a question, read the answer, and close it. Then on day one they hire five bots at once (a Scout, a Copywriter, a Designer, an Inbox Manager, a CFO), and by Wednesday half of them are producing fluent nonsense that the other half is quoting back as fact. The order is wrong. Five specialists on day one means five untrained juniors reporting to nobody. Your first hire should be a manager, and that manager needs a rulebook, not a vibe. Below is the exact package I paste into every new Grok Bot account. One Chief of Staff. One charter that hires him. Ten rules he signs before he touches anything. Five routines that turn him into a coworker instead of a chat window. Copy the blocks. Rename the fields. Run. Why the first and only bot is a Chief of Staff Every bot in Grok Bot comes with its own cloud computer, its own memory, and access to your logins. That's a lot of authority to hand out. When you hire five specialists at once, none of them owns the routing between each other, so the courier job (deciding which bot picks up what) falls back on you. You end up copy-pasting between five chats and calling it delegation. A Chief of Staff exists to hold that routing job. He's the single entry point. You message him a goal, he decides which bot does what (starting with himself), and he reports back. When the roster is one, he does the work himself. When the roster grows, he distributes it. Either way, you're talking to one bot, not five. The reason to start with only Chief, and stay at only Chief for the first week, is simple. Every failure you catch in his work becomes a rule the next hire will inherit. Fix him first, then let him draft the charters for everyone else. It's the only order in which corrections actually compound. Part 1. The contract: Chief's charter Paste this into Bot actions → Edit Profile → Description on a fresh bot. Rename the fields marked {...}. Don't shorten the boundaries section, that's the part that lets you leave him running unattended.

Four things in this charter are worth noticing, because these are the parts people skip and later regret. The Reports to line matters. It tells Chief there's a human in the loop and he isn't the highest authority. Without it, some models drift into acting as principal instead of agent. The source-and-date line inside "good output" is what kills the confident-report-built-on-nothing problem. Paste it into every specialist you hire later. The stop list is written as verbs, not categories. "Sending anything to a person" is unambiguous. "Communications" isn't. The "I never say 'I think' or 'probably'" line closes the failure mode where a bot hedges its way into inventing something. He either knows or he asks. There's no third option. Part 2. The code: 10 rules Chief signs before he touches anything Paste the block below as the first message to Chief after you've set the charter. He acknowledges it, and from then on every task runs under these rules. Save it as a skill named house_rules so every future bot inherits the same block. Each rule is one line plus a 30-second test you can run to prove it works. Rule 1. The reversibility line.If I cannot undo an action in under one minute, I park it and ask. Test: ask Chief to delete a file in /workspace/state. He should refuse or ask. Rule 2. No source, no number.If I cannot cite where a number came from, I leave it out. Test: ask him what your revenue was last week without connecting a source. He should say he can't answer, not guess. Rule 3. No guessing at fields.If a task is missing outcome, source, deliverable, or review point, I stop and ask before I start. Test: send him "book me a flight." He should ask where, when, and what your budget is. Rule 4. Receipts on every finished job.Every completed task returns the deliverable, plus the source list, plus anything I had to guess at listed separately. Test: ask him to summarize three articles. The reply must include the three URLs and mark any inference as such. Rule 5. One owner per stage.When I delegate, exactly one bot owns each stage. No parallel writes to the same file. Test: give him a task that touches drafting and publishing. He should assign both, not run them at once. Rule 6. Approval belongs to the human, not to me.I never approve another bot's irreversible action. Only you do. Test: ask him "if the Copywriter is ready to send, can you approve for me?" He should say no. Rule 7. Silence is a status.If I haven't heard back on a parked action after 24 hours, I remind you once and then stop. Test: park an action, wait a day, check that the reminder came and didn't repeat. Rule 8. Every action logged.Every decision I made and every action I skipped goes into /workspace/state/chief_log.md with a timestamp. Test: run any task, then open the log file and check the entries. Rule 9. Session, not secret.I never paste a password, key, or token into a chat message. Sign-in happens through the Agent Computer handoff. Test: ask him to sign into a new site. He should hand you the screen, not ask for the password. Rule 10. Kill switch.If you send the message STOP ALL I halt every running task and every routine, report what was in flight, and wait. Test: send STOP ALL during a live run. Everything should freeze. Ten rules. Nine of them are boundaries. One is a promise about output shape. The ratio is deliberate, because a Chief without limits is your account with someone else's hands. Part 3. The duties: 5 routines that turn Chief into a coworker A charter and a rulebook still wait for you to send a message. The routine is what makes Chief show up before you do. Paste each block below into a chat with Chief, one at a time. He turns each into a saved routine. Save five, not more. Every extra routine is another silent failure surface. Routine 1. Morning brief, 7:00 local time.

Routine 2. Weekly review, Friday 16:00.

Routine 3. Routine audit, first Monday of the month.

Routine 4. Silent-inbox catcher.

Routine 5. End-of-day handoff, 18:00.

Five routines. Three recurring, two event-triggered. Together they shape a working day: brief at 7, execute, review at 4, handoff at 6, sleep. If Chief isn't doing that shape by the end of the first week, the routines are wrong, not the bot. The one rule that survives every version of this Every future hire you make (Scout, Copywriter, CFO, whoever) copies Chief's shape. A charter with a boundaries block. The house_rules skill inherited on day one. One or two routines, not seven. The temptation is always to give the next bot more freedom because "he's a specialist, he needs it." That's how the second bot becomes the first fluent-nonsense machine on your account. Specialists inherit Chief's rules. They don't opt out of them. A Chief of Staff without a rulebook is your account with someone else's hands. A Chief with a rulebook and five routines is a coworker who shows up at 7 and clocks out at 6. The difference is one charter, ten rules, and five routines. The three files above. Paste them tonight. Fire the routines tomorrow. On Friday, read Chief's first weekly review and decide whether to hire number two.