6c7eed7580
Fresh history cut from cynarAI/evoo antigravity-handoff/project-timeline (Voice First + project timeline). Brand docs/titles as evOo; keep @rakazo/* packages as tech debt. Excludes node_modules, caches, secrets, voice blobs.
2.5 KiB
Pack: CasJam product heads (Head + Growth + Maintainer)
Brian Casel's v2 roster, from this post (29 Aug 2026). There is no official https://x.ai/bot/… share in the post or the screenshot. Do not invent one. One share still equals one bot, so a roster is assembled, not imported.
Quoted v1 (Chief / Heads / Doers / Reviewers) is here. v2 dropped the shared bench and reviewers. Each product now owns three seats.
What the screenshot actually is
One Grok Bot account. Folders per brand. Four brands in his case: Brian Casel, Builder Methods, Flywrite, Mimeo. Each folder has:
| Seat | Job |
|---|---|
| Head | Product roadmap, feature orchestration, weekly report to Chief, inbound from you and Chief |
| Growth | Pitch growth experiments, project-manage them, ship them, track, document learnings, report to Chief |
| Maintainer | Recurring chores, admin, maintenance |
Plus one portfolio Chief above the folders (intake, priorities, the week).
Quota math: 1 Chief + 4 × 3 = 13 bots. That is already a quarter of the 50-bot account cap, and they all share one computer. Copy the shape, not his four brands, unless you actually run four products.
How to assemble (nothing to Add from his post)
- Create a new Chief, or start from the official CoS starter in docs/official-starters.md. First task is digest only. Do not send mail or change meetings.
- For one product you actually own, create three new bots: Head, Growth, Maintainer. Put the job from the table in each description. Reconnect only the plugins that seat needs.
- Point Chief at those three in chat once: Heads report weekly, Growth does not ship without Head seeing it, Maintainer does not invent work.
- Optional imports from this catalog if a seat matches: Fixer as an operator, Work as a standing inbox. Still reconnect your own tools.
- Do not enable routines until the first read-only task on each seat looks right. Do not import twelve random catalog rows to "fill" the org chart.
v1's Doers (builder, designer, writer, video) and Reviewers are extra bots. Add a Doer only when a Head has a named job that week. Reviewers stay gates: they do not ship.
Why a pack
A public share copies one bot's identity, not a company. CasJam's screenshot is a layout, not a template. The useful part that travels is the three-seat-per-product rule and the cap math.