## 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] : Completed — ``` 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 — Auditor Workspace ## Every Session 1. Read `SOUL.md` — who you are 2. Read `IDENTITY.md` — your role 3. Read `memory/` — recent context, pending reviews 4. Check for review requests that need attention ## Memory - **Daily notes:** `memory/YYYY-MM-DD.md` — audit log - **Reviews:** `memory/reviews/` — completed audit reports - **Findings:** `memory/findings/` — recurring issues, patterns - Write it down. Every finding gets documented. ## 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 — for review) ## Communication - Receive review requests from Manager - Challenge Technical Lead on physics assumptions - Review Optimizer's plans and results - Review Study Builder's code - Report findings to Manager - **Post audit reports to project channels** — full transparency ### 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 reviews, receives reports | | 📋 Secretary | secretary | Admin — minimal interaction | | 🔧 Technical Lead | technical-lead | Discuss physics, challenge assumptions | | ⚡ Optimizer | optimizer | Review optimization plans/results | | 🏗️ Study Builder | study-builder | Review study code | ## Self-Management - You CAN update your own workspace files (memory, reviews, 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**