11 席——多席 Grok @bot 艦隊 我對 coordinator 說話，他調度艦隊……

11 席——多席 Grok @bot 艦隊 我對 coordinator 說話，他調度艦隊 這是我們真正在用的營運圖。一個 coordinator 席，加上專職席。人類只碰送出、花錢、合併。 誰負責什麼： 1. Auditor 席 → 基礎稽核，把 Critical/High 推給 SEO = @seoutils_app 2. SEO 席 → 修正和 pull requests（我合併）- @dataforseo 3. Ads 席 → 只建議（沒我點頭不能真花錢）用 Google Ads MCP 4. Copy 席 → 部落格和頁面，向 Designer 要圖 5. Social 席 → Postly 草稿，向 Designer 要素材（不做 GBP） @postlysocial 6. GBP 席 → listing 營運，向 Designer 要版面 - 用 Grok bot 的 Cloud browser 7. Linkbuilder 席 → Incogniton 送件，上線前四關 - 100 個帳號 / 代理 8. Outbound 席 → 只寫外展草稿（永不送出）- ppcreveal(dot)ai - 掃描正在跑 Ads 的公司 9. Research 席 → 近 30 天資料包 @slashlast30days 10. Designer 席 → 所有視覺（Higgsfield） @higgsfield_ai 11. CEO coordinator 席 → 在我的核准閘下調度艦隊 常設時鐘： 1. 每日 X 草稿 + hook 研究（清晨） 2. 多通路社群 週二到週五 3. GBP 週一／週三／週五 4. 每週部落格 週二 5. 月底稽核 6. 每天早上用各 agent 的 SOP 跑 Obsidian Vault lint - 和 Hermes 共用 真相層： 1. Obsidian → 每席可長期用的 SOP 2. Nifty → 工作紀錄和 VA 3. Grok memory → 進行中的事實 4. Hermes → 只給我們 QUERY 5. Git + Cursor + Astro → 工作需要時的程式碼和網站 底下那張圖才是真規則：每條路徑都停在我核准。 bot 起草、排隊。我按送出、花錢，或合併。 工具： 1. Grok Bot → 席位、例行、記憶 2. Obsidian + Nifty → SOP 和工作紀錄 3. Hermes → 查詢保險庫 4. Postly / Higgsfield / Incogniton → 通路和創意營運 5. Cursor

原文：11 seats - Multi-seat Grok @bot fleet I talk to coordinator, he runs the fleet This is the ops map we actually use. One coordinator seat plus specialist seats. Humans stay on send, spend, and merge. Who owns what: 1. Auditor seat → foundation audits, pushes Critical/High to SEO = @seoutils_app 2. SEO seat → fixes and PRs (I merge) - @dataforseo 3. Ads seat → recommend-only (no live spend without me) using Google Ads MCP 4. Copy seat → blogs and pages, asks Designer for images 5. Social seat → Postly drafts, asks Designer for creatives (no GBP) @postlysocial 6. GBP seat → listing ops, asks Designer for plates - using Cloud browser in Grok bot 7. Linkbuilder seat → Incogniton submits, four gates before live - 100 accounts / proxies 8. Outbound seat → outreach drafts only (never send) - ppcreveal(dot)ai - scanning companies running Ads 9. Research seat → last-30-days packs @slashlast30days 10. Designer seat → all visuals (Higgsfield) @higgsfield_ai 11. CEO coordinator seat → routes the fleet under my approve gate Standing clocks: 1. Daily X draft + hook research (early morning) 2. Multi-channel social Tue–Fri 3. GBP Mon/Wed/Fri 4. Weekly blog Tuesday 5. End-of-month audit 6. Obsidian Vault lint every morning with each agent SOPs - sharing with Hermes Truth layers: 1. Obsidian → durable SOPs per seat 2. Nifty → work log and VAs 3. Grok memory → working facts 4. Hermes → QUERY only for us 5. Git + Cursor + Astro → code and site work when the job needs it The diagram at the bottom is the real rule: every path ends at me approve. The bots draft and queue. I hit send, spend, or merge. Tools: 1. Grok Bot → seats, routines, memory 2. Obsidian + Nifty → SOPs and work log 3. Hermes → query vault 4. Postly / Higgsfield / Incogniton → channel and creative ops 5. Cursor + Astro + Git → build and ship 6. DataForSEO / SEO Utils / PPC Reveal Why it matters: 1. One person can run specialist loops without hiring a VA per channel 2. Handoffs are explicit (audit → SEO, copy/social/GBP → Designer) 3. Approvals sit where money and reputation live If your “AI agency” is still one chat window and a pile of prompts, you’re missing the seat map.

整合