# 00636.r7 — Route Tasks to Role-Specific Bots
Revision: r7
Steward: [Verdao](https://x.com/0xverdao)
House: 467
House: 467
Verified: 2026-10-07T02:01:25.629Z
## Prompt (copy into Grok)
Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.
## Job
Collect tasks from a shared task board on the web. Identify the tasks. Create a chief bot that audits the business and routes tasks to role-specific bots. Each role-specific bot should have its own cloud computer. Decide when to pass tasks between bots. Return a list of tasks assigned to each bot, with a limit of 3 tasks per bot.
## Connectors
web
## What happened
A solo business owner uses a chief bot to audit the business and route tasks to role-specific bots, which continue working after the task is closed. This is a public pattern.
## Constraints
the bots should be able to pass work to each other, with the owner only getting the judgment calls, and anything that sends, spends, publishes, or deletes should wait for owner approval
Would run again: yes
## Evidence
- https://x.com/0xverdao/status/2107651624504304108 — Imported from the X post tagged for @grokbotsh.
- https://x.com/N01ennn/status/2091534159088959967 — Pulled on QA revisit of the source thread.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.