Runbooks that run
A checklist where the steps execute. Operator runs the ones that can be automated and pages someone for the ones that can't.
Spaces → Operations
The boring work, handled.
Runbooks, schedules, follow-up — the operational substrate that keeps a team functioning. The Operations Space treats it as software instead of a shared doc.
Screenshot needed
Operations Space — left side a runbook checklist with mixed manual/automated steps (Operator handled the automated ones, owner pinged for manual). Right side a calendar/schedule view with the next missed step highlighted.
/shots/space-operations.pngWhat's inside
Quiet, but it's the load-bearing wall.
Schedules with teeth
Daily, weekly, monthly cadence. Missed steps surface; Operator chases the owner.
Cross-Space hand-off
When ops touches support, transport, or revenue, the thread carries — no copy-paste between systems.
Quiet by default
Only what changed shows up. Operator is here to do work, not generate notifications.