# TOOLS.md — Manager

## Shared Resources
- **Atomizer repo:** `/home/papa/repos/Atomizer/` (read-only)
- **Obsidian vault:** `/home/papa/obsidian-vault/` (read-only)
- **Job queue:** `/home/papa/atomizer/job-queue/` (read-write)

## Skills
- `atomizer-protocols` — Company protocols (load every session)
- `atomizer-company` — Company identity + LAC critical lessons

## Key Files
- QUICK_REF: `/home/papa/repos/Atomizer/docs/QUICK_REF.md`
- Protocols: loaded via `atomizer-protocols` skill

## Agent Communication
- **`orchestrate.sh`** — Synchronous delegation with result return (PRIMARY)
  - Script: `/home/papa/atomizer/workspaces/shared/skills/orchestrate/orchestrate.sh`
  - Usage: `bash orchestrate.sh <agent> "<task>" [--timeout N] [--context file] [--retries N] [--validate] [--caller manager] [--no-deliver]`
  - Returns structured JSON: `{"status":"complete|partial|blocked|failed", "result":"...", "confidence":"high|medium|low", "notes":"..."}`
  - Handoff dir: `/home/papa/atomizer/handoffs/`
  - **Max 2 attempts total** (1 original + 1 retry). Then stop and report failure.
  - **Chaining:** Save result to file → pass via `--context` → describe contents in task text
- **`workflow.py`** — YAML workflow engine for multi-step orchestration
  - Script: `/home/papa/atomizer/workspaces/shared/skills/orchestrate/workflow.py`
  - Wrapper: `/home/papa/atomizer/workspaces/shared/skills/orchestrate/workflow.sh`
  - Usage: `python3 workflow.py <workflow-name-or-path> [--input key=value ...] [--caller manager] [--dry-run] [--non-interactive] [--timeout N]`
  - Workflows dir: `/home/papa/atomizer/workspaces/shared/workflows/`
- **`metrics.py`** — Orchestration metrics and stats
  - Script: `/home/papa/atomizer/workspaces/shared/skills/orchestrate/metrics.py`
  - Usage: `python3 metrics.py [json|text]`
  - Shows: per-agent success rates, latencies, workflow completion stats
- **Agent Registry:** `/home/papa/atomizer/workspaces/shared/AGENTS_REGISTRY.json`
- **`[DELEGATE:agent "task"]` syntax does NOT work** — never use it.
- Prefer `sessions_spawn` / `sessions_send` for native OpenClaw orchestration inside this workspace.
- Use `orchestrate.sh` only when you explicitly want that shared orchestration layer.
- Use the `message` tool for user-visible channel delivery.

## Knowledge Base
- LAC insights: `/home/papa/repos/Atomizer/knowledge_base/lac/`
- Project contexts: `/home/papa/repos/Atomizer/knowledge_base/projects/`

## 📊 Mission-Dashboard (MANDATORY)
The Atomizer-HQ Mission-Dashboard is the **single source of truth** for all tasks.
- **Dashboard:** http://100.68.144.33:8091
- **Data:** ~/atomizer/mission-control/data/tasks.json
- **CLI:** ~/atomizer/workspaces/shared/mc-update.sh
- **Protocol:** ~/atomizer/workspaces/shared/skills/mission-control-protocol.md

### Commands
```bash
MC=~/atomizer/workspaces/shared/mc-update.sh
$MC add "Title" "Description" [status] [project] [priority]
$MC start <task_id>
$MC comment <task_id> "Progress update"
$MC subtask <task_id> <sub_id> done
$MC complete <task_id> "Summary of work done"
$MC status <task_id> <new_status>
```

### Rules
1. **No shadow work** — every project/orchestration MUST have a dashboard task
2. **Update task before posting to Slack** — dashboard is the record, Slack is discussion
3. **Log progress as comments** — this is the audit trail