For the person running classes
Your day, in five minutes
The system does the watching, drafting, and filing. Your job is small and high-leverage: feed it two things, and approve what it writes. Here is the whole loop.
The daily rhythm
The Morning Brief lands
A note appears in your Notion Inbox: what is due today, what is overdue, what is new, and a link straight to Mission Control. Skim it for surprises.
Open Mission Control
One screen: gauges up top, today's sessions, the email triage queue, and the approve-and-send queue. This is your cockpit for the day.
Clear the approval queue
Read each draft the system wrote. If it is good, tick approve, then paste it into Campaign Monitor or Telegram and send. Nothing leaves until you do.
Tick things done
Check off commitments as you clear them. The dashboard writes it straight back to Notion and stamps who closed it, with a 7-second undo if you misclick.
Feed the system
Drop the class deck PDF onto the session page, and set the recording URL once it lands. Those two acts are the fuel that lets every draft write itself.
What you touch, what the system touches
You, five small things
- Drop the class deck PDF on the Notion session page
- Set the recording URL when it arrives
- Tick the four progress checkboxes as you go
- Read, approve, and send the Outbox drafts
- Capture a lesson after class if something broke
The system, everything else
- Read every meeting and email, filter for relevance
- Draft the reminders, recaps, and community posts
- Audit each deck for stale links and coupons
- File tasks, context, and decisions into the brain
- Watch its own cost and health, back up nightly
One session, four checkboxes
Every class is a checklist in Class Ops v2 with four progress boxes. The system drafts the work for each; you confirm and tick. When all four are green, the session rotates out of your view.
Reminder Sent
T-7 to T-0 reminders draft themselves into the queue. You verify they went out, then tick this.
Community Post
The deck-grounded community post drafts once the deck is attached. Approve and post, then tick.
Recording Uploaded
When the video lands you set the recording URL. The system also tries to catch it from email on its own.
Recap Sent
Recap Producer drafts the recap from deck plus recording. Approve and send, then tick. Session complete.
The promise that protects you
No silent failures, ever
If the deck is missing, the system makes you a task that says "attach the deck," instead of guessing. If the recording URL is missing, it waits and asks. A bad config raises one alert that clears itself when you fix it. The system never fabricates and never fails quietly: if something is blocked, it lands on your list in plain language.
When something looks off
A draft I expected is not in the Outbox
Check the session has a deck attached and is inside the look-ahead window. If a producer hit a snag it raises a Pipeline Issue, visible in the dashboard's pipelines section. Most resolve themselves on the next run.
The dashboard shows an error count
The Issue Triage worker auto-closes stale, fixed, and recovered issues every morning and routes the real ones to your task list. A red count is rarely an emergency; open the pipelines section to see what it routed.
I need to stop a worker right now
Each pipeline has a Halt Flag in the Pipeline State database; set it and the next run exits before doing anything. The dashboard has its own DASHBOARD_ENABLED and WRITES_ENABLED switches. See the runbooks below.