Atomizer/hq/workspaces/webster/TOOLS.md

TOOLS.md — Webster

Shared Resources

• Obsidian vault: /home/papa/obsidian-vault/ (read-only)
• Atomizer repo: /home/papa/repos/Atomizer/ (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

• sessions_send — Direct message to another agent
• sessions_spawn — Delegate complex task to sub-agent
• Slack @mentions — Primary communication in project channels

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

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