Files / Config

MISSION_CONTROL.md

# MISSION_CONTROL.md - OpenClaw Mission Control

Central dashboard for Khaled's OpenClaw orchestration setup.

Mission Control is the dashboard over the live SQLite operating state. The canonical state for projects, agents, tasks, runs, events, workflows, artifacts, decisions, and approvals is `data/mission-control.sqlite3`.

Keep this file concise and human-readable. Agents should update live state through `mission_control.bridge`, `python3 -m mission_control.cli bridge ...`, `mission_control.service`, or the FastAPI API, not by editing markdown tables or writing raw SQL.

## Core Rules

| Rule | Meaning |
| --- | --- |
| Core system | OpenClaw / Fakker is the core orchestration system. |
| State location | Live orchestration state lives in `data/mission-control.sqlite3` inside this workspace. |
| Paperclip boundary | Paperclip is external/protected unless Khaled explicitly activates it. |
| Delivery contract | Every active task needs a clear expected output or deliverable. |
| Concision | Keep this file short; move live details to the database and durable procedures to linked docs. |
| Intake | Raw work starts in `INBOX.md`, gets routed by `TRIAGE_RULES.md`, and owners come from `AGENT_ROSTER.md`. |

## Current Snapshot

| Field | Value |
| --- | --- |
| Last updated | 2026-05-24 |
| Active focus | Operate Mission Control from the live SQLite database. |
| Delivery mode | Building |
| Top blocker | None for Mission Control setup. |
| Next action | Use `python3 -m mission_control.cli bridge board-summary` for current live task state. |
| Expected output | Database-backed workspace dashboard that routes status, tasks, domains, owners, routines, and outputs. |

## Delivery Modes

| Mode | Use When |
| --- | --- |
| Planning | Defining goals, scope, owners, and expected outputs. |
| Building | Implementing backend, frontend, infra, automation, or workflow changes. |
| Debugging | Diagnosing broken systems, errors, incidents, or regressions. |
| Reviewing | Checking diffs, designs, code, tests, or decisions before acceptance. |
| Reporting | Producing status summaries, project updates, decision logs, or execution reports. |
| Monitoring | Watching servers, processes, routines, automations, and integrations. |

## Command Center Board

Canonical board state is returned by:

```bash
python3 -m mission_control.cli bridge board-summary
```

The table below is only a short human summary of the live DB.

| Task | Domain | Owner | Mode | Status | Blocker | Expected Output |
| --- | --- | --- | --- | --- | --- | --- |
| Maintain Mission Control | backoffice | Fakker | Building | Active | None | Live SQLite state with concise dashboard docs and command routing. |
| Define daily status checklist | backoffice | Fakker | Planning | Pending | None | Checklist for daily status summaries. |
| Add server health runbook | infra/DevOps | Fakker | Planning | Pending | None | Repeatable server/OpenClaw health procedure. |
| Add heartbeat/backoffice routine | automation | Fakker | Planning | Pending | None | Routine for periodic checks and workspace updates. |

## Intake Summary

| Queue | Source | Status | Next Action |
| --- | --- | --- | --- |
| Raw inbox | `INBOX.md` | Ready | Add raw tasks, ideas, bugs, notes, and requests here. |
| Triage rules | `TRIAGE_RULES.md` | Ready | Classify, prioritize, split, assign, review, or archive inbox items. |
| Agent roster | `AGENT_ROSTER.md` | Ready | Use planned owner roles and boundaries for assignments. |

## Delivery Workstreams

| Domain | Repo / Path | Branch | Task | Owner | Status | Blocker | Test Status | Expected Output |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| backend | TBD | TBD | No active backend delivery task. | Fakker | Pending | Awaiting explicit goal. | Not started | Backend task plan or implementation when assigned. |
| frontend | TBD | TBD | No active frontend delivery task. | Fakker | Pending | Awaiting explicit goal. | Not started | Frontend task plan or implementation when assigned. |
| infra/DevOps | /home/node/.openclaw/workspace | master | Add server health runbook. | Fakker | Pending | None | Not started | Runbook in `RUNBOOKS.md`. |
| QA/testing | TBD | TBD | No active QA task. | Fakker | Pending | Awaiting delivery work. | Not started | Test plan, verification result, or bug report. |
| automation | /home/node/.openclaw/workspace | master | Add heartbeat/backoffice routine. | Fakker | Pending | None | Not started | Routine definition in workspace docs. |
| integration | /home/node/.openclaw/workspace | master | Keep Telegram command routing aligned. | Fakker | Active | None | Docs review | `COMMANDS.md` points status commands to Mission Control first. |
| backoffice | /home/node/.openclaw/workspace | master | Create and maintain Mission Control. | Fakker | Active | None | Docs review | `MISSION_CONTROL.md` created and linked to command workflow. |

## Agents & Ownership

| Agent | Role | Current Assignment | Can Touch | Escalation |
| --- | --- | --- | --- | --- |
| Fakker | Main orchestrator | Coordinate OpenClaw workspace, tasks, docs, reports, routines, and delivery work. | OpenClaw workspace and explicitly assigned project paths. | Ask Khaled before destructive, external, privacy-sensitive, or protected-project actions. |
| Future agents/subagents | Specialized delivery workers | None active. | Only assigned scope. | Report owner, status, blockers, tests, and expected output back to Fakker. |
| Planned roster | Owner map | See `AGENT_ROSTER.md`. | Assigned scopes only. | Produce clear deliverables and review notes. |

## Projects Index

| Project | Status | Source |
| --- | --- | --- |
| OpenClaw / Fakker orchestration | Active | `data/mission-control.sqlite3` |
| Paperclip | External / Protected | `data/mission-control.sqlite3` and `PROJECTS.md` boundary notes |

## Routines & Automations

| Routine | Owner | Schedule / Trigger | Status | Expected Output |
| --- | --- | --- | --- | --- |
| Daily status summary | Fakker | On `status`, `today`, meaningful heartbeat, or end-of-day request. | Pending checklist | Short completed/active/blocked/next summary. |
| Heartbeat/backoffice routine | Fakker | Heartbeat or explicit request. | Pending definition | Operational checks captured in workspace state. |
| Server health summary | Fakker | On `server`, incidents, or scheduled review. | Pending runbook | Concise health summary with evidence and next step. |

## Integrations

| Integration | Purpose | Status | Boundary |
| --- | --- | --- | --- |
| Telegram | Main away-from-web command channel. | Active | Keep replies short and practical unless detail is requested. |
| OpenClaw workspace | Source of orchestration state. | Active | Keep Mission Control and related docs here. |
| Paperclip | Separate Docker app. | Protected / external | Do not modify or build around it unless Khaled explicitly activates Paperclip. |

## Outputs Due

| Output | Trigger | Status | Save Location |
| --- | --- | --- | --- |
| Daily status summary | `status`, `today`, heartbeat with meaningful updates, or end-of-day request. | Available once checklist is defined. | `memory/YYYY-MM-DD.md` |
| Project tracker update | Project state or boundary changes. | Active | `PROJECTS.md` |
| Server health summary | `server`, incident, or scheduled review. | Pending runbook | `memory/YYYY-MM-DD.md` and `RUNBOOKS.md` for procedure. |
| Backoffice checklist | Heartbeat maintenance or weekly review. | Pending routine | `TASKS.md` and `memory/YYYY-MM-DD.md` |
| Decision log | Durable preference, boundary, architecture, or operating-rule decision. | Active | `DECISIONS.md` |
| Weekly execution report | Weekly review or explicit request. | Pending | `memory/YYYY-MM-DD.md` |

## References

| File | Role |
| --- | --- |
| `PROJECTS.md` | Project boundaries and sources of truth. |
| `TASKS.md` | Human-readable task summary; live task state is in SQLite. |
| `MISSION_CONTROL_DB.md` | Database architecture, schema, initialization, and agent access rules. |
| `data/mission-control.sqlite3` | Live Mission Control operating state. |
| `mission_control/bridge.py` | Fakker-facing local bridge for task creation, assignment, movement, detail, history, intake, and board summaries. |
| `mission_control/cli.py` | Controlled command-line access for agents. |
| `INBOX.md` | Raw intake queue for untriaged work. |
| `TRIAGE_RULES.md` | Classification, priority, splitting, assignment, review, and archive rules. |
| `AGENT_ROSTER.md` | Agent/subagent roles, capabilities, boundaries, and expected outputs. |
| `DECISIONS.md` | Durable decisions with date, reason, and impact. |
| `RUNBOOKS.md` | Repeatable server, OpenClaw, and debugging procedures. |
| `OUTPUTS.md` | Output/report definitions. |
| `COMMANDS.md` | Telegram command behavior. |
| `memory/YYYY-MM-DD.md` | Daily raw history, status notes, and reports. |