Hire by Business Lane. Isolate the Irreversible.

One inbox splits the work. Split by business lane, not by app name. Money gets its own teammate. Bots are not a security boundary.

What Grok Bot adds is an org, not a feature list. Officially: a dispatcher sits on top, specialists sit on each lane, they pass work, and they pull you in only for judgment calls.xai-bot Community handbooks write this as chief of staff plus lanes, and they keep repeating: one more bot is not one more security wall — files and login state are shared.grokbot-playbook

After reading, you should be able to answer:

• Why does splitting by app name fall apart?
• Why must money sit on its own teammate?
• When should you turn a path into a replayable flow?

By lane, not by app

“One for mail, one for calendar, one for sheets” makes them wait on each other inside the same piece of business. Split by lane: intel, admin, content, money. The dispatcher is the only inbox, so you are not calling five people directly. Handoffs are tickets: object, result, stop — not pasted chat.

Grow at most one role a week. Kill idle roles. Expanding before a closed loop only piles titles.

Money alone, irreversible stops

Pay, refund, bind a card: one teammate, not mixed with other duties. Sensitive acts go through review before they run — officially, auto-review sits on those steps.xai-bot That is red lines in teammate shape: the act is irreversible, so it stops. Not because a menu is named review.

No secrets in chat. No new tools until you say so. Bots are not a security boundary: files and sessions on the shared computer are visible to each other by default.

Replay a path only after two runs

Fold a fixed, low-judgment path into a replayable flow only after you have run it through the five steps and corrected it. Correct in words. Do not silently redo. Check the first runs. The general skeleton is a reusable brief.