<aside> 💡 Use case: know exactly where the system waits for you, how to say yes or no, and how to stop everything in one step.

</aside>

The 6 owner controls

Control Where it lives What it does
Owner dashboard drafts/briefs/YYYY-MM-DD-week-plan.md One view of what is running this week and what waits
Approval queue queue/needs-your-ok.md Anything above your approval bar waits here
Activity log logs/activity.md Every action every agent took, one line each
Permissions "Who writes where" in CLAUDE.md and each agent's tools: line Which agent can touch which folder and tool
Alerts "Alert me right away" in owner/approval-bar.md Puts URGENT items at the top of the queue
Kill switch owner/STOP Stops every agent before its next action

How the two queue files work

<aside> 📥 queue/needs-your-ok.md: decisions only you can make. The orchestrator adds an item whenever something sits above your approval bar: a spend, a reply to a negative review, an offer, an off-calendar post. Each item says what will happen, why it waits, which draft it is about and what it costs.

</aside>

<aside> 🎙️ queue/held-for-voice-review.md: drafts that failed the voice check. A department adds the draft here with the exact rule it broke and the line that broke it, instead of quietly fixing it. Nothing in this file goes out until you clear it.

</aside>

<aside> 🗂️ Both files share the same shape: a format block at the top, an ## Open section where new items land, and a ## Done section where the orchestrator moves every decided item. Only you tick a box. Agents never do.

</aside>

How to approve

<aside> ✅ Three steps:

  1. Open queue/needs-your-ok.md and read the item and its draft
  2. Tick one box: change - [ ] Approve to - [x] Approve, or tick Reject and write why in "Owner note"
  3. Tell the orchestrator, so it acts on your ticks: </aside>
Process my approvals in queue/needs-your-ok.md.

<aside> 🎙️ For held drafts, fix the draft yourself and tick "Fixed: send it on", or tick "Drop it". Then:

</aside>

Process the held items in queue/held-for-voice-review.md.

<aside> 📄 What happens next: approved items are briefed to Publishing & social to schedule. Rejected items are logged and dropped or re-briefed from your note. Every decision moves to ## Done and gets a line in the activity log.

</aside>

The kill switch

<aside> 🛑 To stop everything, create an empty file called STOP in owner/:

</aside>

touch owner/STOP

<aside> 🧱 CLAUDE.md makes every agent check for this file before every action. While it exists, nothing is written, scheduled, sent or spent. Each agent that hits it logs one stopped: owner/STOP present line and tells you the system is paused. Agents cannot create, edit or delete it: only you can.

</aside>

<aside> ▶️ To resume, delete the file and start a fresh run:

</aside>

rm owner/STOP
Use the orchestrator agent to run this week's loop.