# Atomizer-HQ Mission-Dashboard Protocol ## Overview The Mission-Dashboard at `http://100.68.144.33:8091` is the **single source of truth** for all Atomizer HQ tasks. All agents MUST use it. ## Dashboard Location - **URL:** http://100.68.144.33:8091 - **Data file:** ~/atomizer/mission-control/data/tasks.json - **CLI tool:** ~/atomizer/mission-control/scripts/mc-update.sh ## Task Lifecycle ``` backlog → in_progress → review → done ``` | Status | Meaning | |--------|---------| | `permanent` | Recurring/standing tasks | | `backlog` | Waiting to be worked on | | `in_progress` | Agent is actively working | | `review` | Done, awaiting human review | | `done` | Approved by Antoine | ## Agent Responsibilities ### Manager - Creates new tasks (`mc-update.sh add`) - Assigns tasks to agents (via comments) - Moves approved work to `done` - ALL new projects/orchestrations MUST get a dashboard task ### All Agents - When starting work: `mc-update.sh start ` - Progress updates: `mc-update.sh comment "update"` - Subtask completion: `mc-update.sh subtask done` - When finished: `mc-update.sh complete "summary"` ### Secretary - Reviews task board during reports - Flags stale in_progress tasks (>24h no update) ### Auditor - Verifies completed tasks meet DoD before review ## CLI Reference ```bash MC=~/atomizer/mission-control/scripts/mc-update.sh # Add new task $MC add "Title" "Description" [status] [project] [priority] # Update status $MC status ATZ-xxx in_progress # Add comment $MC comment ATZ-xxx "Progress update: completed phase 1" # Mark subtask done $MC subtask ATZ-xxx sub_001 done # Complete (→ review) $MC complete ATZ-xxx "Summary of what was done" ``` ## Rules 1. **No shadow work** — if it's not on the dashboard, it didn't happen 2. **Update before Slack** — update the task, THEN discuss in Slack 3. **Every orchestration = a task** — Manager creates the task BEFORE spawning agents 4. **Comments are the audit trail** — agents log progress as comments, not just Slack messages