Select Your Operating System
Terminal commands, shell scripts, and scheduling configurations adjust dynamically.
Bot Team Architecture & Company Handbook
Design a collaborative bot team with distinct roles rather than an ephemeral chat. As Roman Huet (Grok Bot Galaxy 3-Day Livestream host and developer advocate) demonstrated on Day 1 [00:30]-[00:38], bots are long-lived teammates with persistent memory, directed by a chief-of-staff orchestrator and guided by a short shared company doc every bot reads [00:24], [04:16].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Confirm creation of your shared company handbook. Paste the first line containing "# Company Handbook":
Writing Bot Descriptions as Operating Manuals ('Soul')
Write each bot's description as its operating manual. Day 1 [00:49] and Day 2 [03:35]-[03:37] emphasize: give each bot one explicit job, definitive boundary rules, and a distinct voice. When operational instructions get overly rigid, rewrite them as guiding principles so the bot adapts gracefully to unexpected real-world edge cases.
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste the line defining the single primary Job of your Chief-of-Staff orchestrator:
Approval Gates, Risk Management & Saying No
Mitigate operational risk using automated classifiers and strict custom approval barriers. As taught on Day 1 [00:43] and [01:16]-[01:17], enforce mandatory human confirmations for external actions (sending emails, modifying databases). Teach bots when to say no, define rigorous criteria for what 'urgent' truly means, and use approve-once trust building as proficiency is proven [04:10], [04:23].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste the line specifying Mandatory Human Approval conditions:
Routines, Event Triggers & Pre-Build Validation
Set up scheduled check-ins and event-driven bots (Slack, CI, Sentry webhooks) while closely monitoring token economics. Day 1 [02:22] and [04:15] show why running polling routines every 15 minutes is wasteful. Validate ideas before writing code: sell to three customers, set up a simple landing page, and perform manual outreach before writing software [02:03]-[02:21], [02:58]-[03:18].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming event dispatcher execution (showing EVENT RECEIVED):
Tool Hierarchy: MCP, Connectors, Computer Use & Cloud Agents
Establish a clear tool hierarchy for autonomous agents: use MCP/connectors when an API exists, Computer Use for legacy non-API interfaces, 'Teach a Task' to turn demonstrations into reusable skills, and cloud coding agents (Cursor, Claude Code, Codex, Antigravity) for software engineering (Day 1 [00:33], [02:25]; Day 2 [01:18], [04:21]).
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste the line describing delegation for Complex Multi-File Codebase tasks:
Shipping an Extensible MVP: Logic Before Graphics
Structure your MVP so AI agents can reliably implement and test it. Day 2 [00:27]-[00:29] and [02:03]-[02:10] prove: prioritize a tight core loop, implement business logic and data structures before visual flair, build scaffolding and debug panels, and document schema signatures with explicit verification checklists [03:27].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming battle engine execution (showing BATTLE: ... damage):
Autonomous Self-Verification & Generator-Critic Pairs
Require agents to prove their own work. Day 1 [04:11], [04:47]-[04:50] and Day 2 [05:25] establish: write deterministic verification CLIs instead of ephemeral one-liners, maintain an active feature map, capture screenshots/videos on PRs, and pair a code generator with an adversarial critic before permitting any merge.
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming test pass (showing PASS: Generator output verified):
Running an Autonomous Software Factory
Operate a continuous software delivery factory on Day 3 [00:14]-[00:17]: keep pull requests small, deploy implementer + verifier agent pairs, configure a QA bot that triggers on green test runs, and use a 'ringleader' bot that launches cloud coding agents that must reproduce a bug before writing a single line of fix code [02:28]-[02:30], [05:08]-[05:09].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming bug reproduction protocol (showing REPRODUCED DEFECT or Authorizing fix branch):
Public Launch, Production Glue & Hostile Inputs
Execute a real public launch (Day 3 [00:19], [01:30]): remember 'if you are not embarrassed by your first version, you launched too late'. Complete production glue (DNS, OAuth redirects). Treat user input as hostile: implement rate limits, handle HTTP 429s, filter profanity, and sanitize prompts to stop prompt injection [01:47]-[01:49], [02:09]-[02:17].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming input guard validation (showing SANITIZED INPUT OK):
Launch Telemetry, Growth & Bot Team Health
Track production telemetry and maintain agent team hygiene: configure a 15-minute launch pulse bot (Day 3 [01:51]), measure retention before revenue, onboard bots with 101/201/301 courses, run weekly dissent and standup meetings, eliminate bot sprawl, and ensure each bot suggests at least one operational improvement every week [03:08]-[03:10], [03:26], [04:18]-[04:41].
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming launch pulse generation (showing Health Status: OPTIMAL):
Livestream Retrospective & Principles of Restraint
Internalize core lessons from the 72-hour retrospective (Day 3 [07:42]-[07:54]): ship the MVP as soon as you have alignment, recognize distribution as your core advantage, exercise restraint by actively un-shipping non-essential features, solve challenges by hand before delegating to bots, keep complete prompt transcripts, and remember that humans provide vision, taste, and judgment.
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste the retrospective rule on Prototype by Hand:
Capstone: Build Your Company of Bots
Build your own operational company of bots for a real-world task: implement a chief-of-staff orchestrator, at least two domain specialist bots with written operating manuals, one scheduled routine, one deterministic verification harness that produces proof, and a 1-page company doc. Compatible with Grok Bot, Antigravity CLI, or any agent CLI.
Execute Step Action
Run this command block in your terminal to implement the architecture:
Paste terminal output confirming capstone company execution (showing VALIDATION: Full cycle confirmed):
Build Bot Better & Wipe Resistance
Enforce mandatory fleet safety protections across your company of bots: complete the per-agent onboarding checklist, understand the variable-limit delete guard demo ($tmp = $env:USERPROFILE), maintain off-volume profile backups (${BACKUP_ROOT:-$HOME/Backups}/llm-profiles), execute a practised restore drill, and enforce fail-closed workspace roots.
Execute Step Action
Run this command block in your terminal to implement the architecture:
Text guards miss variable-derived deletions ($tmp = $env:USERPROFILE). Full protection requires: path inspection, off-volume backups, and a non-destructive restore drill.
2. Variable-Limit Delete Guard Demo
$tmp = $env:USERPROFILE; $literal = $env:USERPROFILE; foreach ($src in @('$tmp','$env:GROK_HOME','python cleanup.py')) { if ($src -like "*$literal*") { "HIT $src" } else { "MISS $src" } }; if ([IO.Path]::GetFullPath($tmp) -eq [IO.Path]::GetFullPath($env:USERPROFILE)) { "REFUSE resolved tmp: it is the user profile. Text guards miss dollar-variables and python cleanup.py. 2026-09-23 Remove-Item of user profile is the example." }
3. Off-Volume Fleet Profile Backup
$dest = "D:\Backups\llm-profiles\$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Force -Path $dest | Out-Null
foreach ($d in @(".agy", ".claude", ".codex", ".grok", ".grokbot", "AppData\Roaming\Grok Bot")) {
if (Test-Path "$env:USERPROFILE\$d") {
robocopy "$env:USERPROFILE\$d" "$dest\$d" /E /NFL /NDL /NJH /NJS
Write-Host "Backed up $dest\$d"
}
}
Get-ChildItem $dest
4. Practised Restore Drill
$drill = Join-Path $env:TEMP "bbb-restore-drill"; New-Item -ItemType Directory -Force -Path $drill | Out-Null; $latestBak = Get-ChildItem "D:\Backups\llm-profiles" -ErrorAction SilentlyContinue | Sort-Object LastWriteTime -Descending | Select-Object -First 1; if ($latestBak) { Copy-Item -Recurse $latestBak.FullName (Join-Path $drill "restored-profile"); Write-Host "bbb-restore-proof: restored real profile from $($latestBak.FullName) into $drill" } else { Set-Content -Encoding ascii -Path (Join-Path $drill "proof.txt") -Value "bbb-restore-proof"; Write-Host "bbb-restore-proof: fallback drill completed in $drill" }
5. Fail-Closed Workspace Policy
Always restrict bot execution roots to designated repositories like $HOME/projects/agent_workspace. Never delegate unattended tasks with blanket auto-approval in the user home directory.
Paste terminal output from the practised restore drill (showing bbb-restore-proof) or variable demo confirming wipe resistance: