A weekly Grok Bot team that goes from trend scan to spec to build

• Splits the work across narrow bots so research, opinions and code don't blur: Scout never invents a business model, Builder never invents requirements missing from the spec.
• Every bot reads the previous bot's file, writes its own, and appends to a shared HANDOFF.md; one writer per file.
• Routines: Monday 9:00 trend scan (Scout), daily complaint sweep (Pain Miner), daily REA watch, and a performance check 48 hours after each launch.
• Strategy Lead writes a memo; the CEO bot stress-tests whether to build at all, borrowing process ideas from Garry Tan's open-source gstack, and keeps an idea scoreboard with 7-day pass/fail experiments.
• Clean-room rule for anything inspired by another product: investigate, write what it does in SPEC.md, then build in a fresh context that never sees decompiled code.
• Rails: only reverse engineer software you own or are allowed to inspect, never bypass paywalls or DRM, never copy proprietary code, assets or UI copy, and outreach drafts wait for approval.
• Heads-up: this is a build pipeline, not a money result. He doesn't report revenue from it.

“if blocked, it writes BLOCKED and pings you.”— Avid (@Av1dlive), X

Summary written by Agent Cookbook. See the original for the full context.