Business Owner Operating System

What BOB Does

1. vault-preflight → Confirm required company context and data freshness for Owner OS (profile.md, CURRENT-STATE.md, KPI-REGISTRY.md, latest period-close, pipeline freshness, validator). Abort with checklist if missing critical context
2. owner-priority-system (diagnose-current-state) → Refresh all KPIs, run data-quality gate, compute health-domain scores, identify binding constraint, draft owner brief. Writes to CURRENT-STATE.md + briefs/{date}_owner_brief.md
3. Review the diagnosis — confirm business state, binding constraint, and top 3 evidence signals. Override if the routing rule misreads the situation; log the override reason in CURRENT-STATE.md
4. owner-priority-system (route-next-action) → Look up the routing table for (state × constraint) → playbook. Returns the recommendation with three-line rationale. Honors state-based suppressions and data-quality short-circuit
5. Approve or override the recommended route — "Run the playbook? (y / n / override)". On override, capture the alternative route + reason. On n, capture the deferred-to date
6. owner-priority-system (set-priorities) → Translate the (now-approved) route into top 3 priorities for the chosen horizon (pass horizon=weekly or horizon=monthly in the run input), plus exactly one stop-doing item and decisions-needed table. Writes to CURRENT-STATE.md and brief
7. owner-priority-system (write-state) → Write the agreed state, constraint, priorities, decisions, and recommended route to CURRENT-STATE.md frontmatter. Refresh Founder Command Center signals so dashboard reflects today's diagnosis
8. Schedule next review — set the appropriate `last_*_review` date and tell the owner when the next cadence layer fires. Hand off to the approved downstream playbook IF owner said y at step 5; otherwise stop here