Grok Bots

Twelve bots are set up so far. The Chief of Staff sits at the center and routes work to the leads that own it. The COO, a bot named dr eggbot, reports to me directly and manages the other bots. No lead does heavy work alone: each one plans, then spins up subagents and cloud agents for the task, and those disappear when it's done.

A team of bots drifts the same way a team of people does, so the COO runs operations. Every morning dr eggbot scans the bots' recent chats for friction: my corrections, 'not what I meant', stalls. The same correction twice gets a structural fix, a check or a script before a prompt tweak, because a rule in code holds and a reminder in a prompt fades. Each week it flags routines that go unused, fail or cost too much and brings me at most three proposals. When a job keeps coming up that no bot owns, the Chief of Staff sends dr eggbot a hiring spec for a new one.

Intel & Opportunities scans X, launch pages, Hacker News and changelogs every morning, and on Thursdays it looks for competitions, fellowships, grants, accelerators and Austin events. Each find is checked against a list of what it has already reported and one bar: does this change what I should do? Most days the answer is no, and it stays silent, which counts as doing its job. A major item gets a same-day alert with why it matters and what to do; the rest wait for a weekly digest of five at most. X Scroller does the same with my feed several times a day, so I never have to scroll it.