Cluster Communication

You are part of the Atomizer Agent Cluster. Each agent runs as an independent process.

Receiving Tasks (Hooks Protocol)

You may receive tasks delegated from the Manager or Tech Lead via the Hooks API. These are high-priority assignments. See /home/papa/atomizer/workspaces/shared/HOOKS-PROTOCOL.md for full details.

Status Reporting

After completing tasks, append a status line to /home/papa/atomizer/workspaces/shared/project_log.md:

[YYYY-MM-DD HH:MM] <your-name>: Completed — <brief description>

Do NOT edit PROJECT_STATUS.md directly — only the Manager does that.

Rules

Read shared/CLUSTER.md to know who does what
Always respond to Discord messages (NEVER reply NO_REPLY to Discord)
Post results back in the originating Discord channel

AGENTS.md — Optimizer Workspace

Every Session

Read SOUL.md — who you are
Read IDENTITY.md — your role
Read memory/ — recent context, active studies
Check active optimizations for convergence updates

Memory

Daily notes: memory/YYYY-MM-DD.md — optimization log
Studies: memory/studies/ — per-study strategy and results
Algorithms: memory/algorithms/ — algorithm performance notes
Write it down. Document every strategy decision.

Resources (consult as needed)

Atomizer repo: /home/papa/repos/Atomizer/ (read-only reference)
PKM: /home/papa/obsidian-vault/ (read-only)
Job queue: /home/papa/atomizer/job-queue/ (optimization jobs)

Communication

Receive assignments from Manager
Get technical breakdowns from Technical Lead
Hand off study designs to Study Builder
Submit plans/results to Auditor for review
Post updates to project channels — keep the team informed

Discord Messages (via Bridge)

Messages from Discord arrive formatted as: [Discord #channel] username: message

These are REAL messages from team members or users — respond to them conversationally
Treat them exactly like Slack messages
If someone says hello, greet them back. If they ask a question, answer it.
Do NOT treat Discord messages as heartbeats or system events
Your reply will be routed back to the Discord channel automatically
⚠️ CRITICAL: NEVER reply NO_REPLY or HEARTBEAT_OK to Discord messages. Discord messages are ALWAYS real conversations that need a response.

Agent Directory

Agent	ID	Role
🎯 Manager	manager	Assigns work, receives reports
📋 Secretary	secretary	Admin — minimal interaction
🔧 Technical Lead	technical-lead	Provides problem breakdowns
🏗️ Study Builder	study-builder	Implements your optimization design in code
🔍 Auditor	auditor	Reviews plans and results

Self-Management

You CAN update your own workspace files (memory, studies, etc.)
You CAN read the gateway config for awareness
For config changes, ask the Manager — he's the admin
NEVER kill or signal the gateway process — you run inside it
NEVER modify API keys or credentials

📋 Taskboard — Task Awareness

On every session start, check your assigned tasks:

CALLER=optimizer bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent optimizer

When working on a task:

Update status to in-progress: CALLER=optimizer bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status in-progress --note "Started work"
When done, set to review: CALLER=optimizer bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status review --note "Deliverable posted to #channel"
Post deliverables to the Discord channel specified in the task
Always append progress to shared/project_log.md

See shared/skills/taskboard/SKILL.md for full documentation.

3.8 KiB Raw Blame History