Inspired by Siosi (@GeorgeSiosi) on Notion as a control plane — chat is ephemeral labor, the page becomes the company — and Texas Twins Dad (@B_doong2daddy) on asking the bot to brief, not do everything. This is a new Tygart article from the stack we actually run. Not a reprint.
Three replies tonight. Same sentence in different clothes.
Bot briefs. Hub laptop is source of truth. Cursor does the work. Chat is last mile, not the company brain.
Notion is the executive card — next move, plain language, the seat. Production lives on the Hub and Origin. If it is not on a card, voice should not depend on it.
Shared board yes. Do not let Notion become the whole shop. Cards for the seat. Files and receipts on the Hub.
What each layer is for
- Grok Bot — brief the work. Goal, handoff, review. Not a second CMS.
- Notion — the card on the chair. Decision, done-when, due, who sits. Not the file system.
- Hub / Origin — pages, repos, receipts, the thing that still exists when the chat tab dies.
- Cursor — the hands. One writer when the write lock is live. See Four Agents, One WordPress Lock.
- Chat window — last mile. A human reads the brief and says yes or no. It is not where the company lives.
Siosi is right that people are stuffing durable objects into Notion because chat evaporates. The miss is treating the page as the factory. A kanban card can hold the next move. It cannot be the WordPress lock, the git history, or the invoice.
Texas Twins Dad is right that the bot should brief instead of “do everything.” Route the code to Cursor and GitHub. Keep Grok in the middle for goal and review. Then stop asking the middle layer to also be the warehouse.
The test
Close the chat. Does the next move still exist on a card? Does the file still exist on the Hub? Can Cursor pick up without re-litigating the thread?
If the answer depends on scrolling a conversation, you built a shop inside a tab. Tabs close.
Will Tygart — Tygart Media.
We write about what we do, including where the work is allowed to live.
Leave a Reply