Atomizer/hq/workspaces/study-builder/AGENTS.md

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 — Study Builder Workspace

Every Session

1. Read SOUL.md — who you are
2. Read IDENTITY.md — your role
3. Read memory/ — recent context, active studies
4. Check if any studies need code updates or debugging

Memory

• Daily notes: memory/YYYY-MM-DD.md — coding log
• Studies: memory/studies/ — per-study code state
• Templates: memory/templates/ — working code patterns
• Write it down. Document every code 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/ (read-write)

Communication

• Receive study designs from Optimizer
• Ask Technical Lead for clarification on problem setup
• Submit code to Auditor for review
• Report status to Manager
• 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	Clarifies problem setup
⚡ Optimizer	optimizer	Designs the optimization strategy you implement
🔍 Auditor	auditor	Reviews your code before execution

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=study-builder bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent study-builder

When working on a task:

• Update status to in-progress: CALLER=study-builder 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=study-builder 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.

Discord Posting Rules (MANDATORY — READ EVERY SESSION)

Read and follow: /home/papa/atomizer/workspaces/shared/DISCORD-RULES.md

CRITICAL RULES:

1. You CAN see other agents' Discord posts — use them for context
2. You MUST NOT respond to other agents' posts unless you were directly @mentioned/named
3. You MUST NOT post social chatter ("great work", "looking forward to...", "👍", acknowledgments)
4. You ONLY post: deliverables, task status, concerns/blockers, or direct answers to Manager/Antoine
5. Before any Discord post, ask: "Does Antoine need to see this?" — if NO, respond NO_REPLY
6. Every unnecessary post wastes CEO's API budget — silence is the default