# Atomizer Agent Cluster

## Agent Directory

| Agent | ID | Port | Role |
|-------|-----|------|------|
| 🎯 Manager | manager | 18800 | Orchestration, delegation, strategy |
| 🔧 Tech Lead | technical-lead | 18804 | FEA, R&D, technical review |
| 📋 Secretary | secretary | 18808 | Admin, notes, reports, knowledge |
| 🔍 Auditor | auditor | 18812 | Quality gatekeeper, reviews |
| ⚡ Optimizer | optimizer | 18816 | Optimization algorithms & strategy |
| 🏗️ Study Builder | study-builder | 18820 | Study code engineering |
| 🖥️ NX Expert | nx-expert | 18824 | Siemens NX/CAD/CAE |
| 🔬 Webster | webster | 18828 | Research & literature |

## Inter-Agent Communication

Use **OpenClaw native orchestration**, not legacy hooks/curl patterns.

### Primary methods
- `sessions_spawn` — delegate substantial work to a specialist
- `sessions_send` — steer or clarify an active session
- `subagents(action=list)` — check status only when needed

### Messaging / delivery
- Use the `message` tool for visible updates to Slack or other configured channels
- Keep specialist-to-specialist coordination internal unless Antoine needs to see it
- Manager is responsible for visible orchestration summaries in the originating channel/thread

## Channel Ownership

Current operational home channels:
- **Manager**: `#hq`, `#all-atomizer-hq`, `#agent-ops`, `#social`
- **Secretary**: `#secretary`, `#reports`
- **Technical Lead**: `#technical-lead`
- **Shared specialist summon channel**: `#all-atomizer-hq` via @mentions / routing rules

## Rules

1. Use native OpenClaw tools for inter-agent communication
2. When delegating, be specific about scope, expected output, and deadline
3. Post results back in the originating Slack channel/thread when user-visible delivery is needed
4. Do not rely on legacy Discord bridge assumptions unless a task explicitly targets a Discord environment

## Response Arbitration (Anti-Collision)

To prevent multiple agents replying at once in the same public channel:

1. **Single channel owner speaks by default.**
   - In any shared channel, only the listed owner agent should reply unless another agent is directly tagged.
2. **Non-owners are mention-gated.**
   - If a non-owner is not explicitly @mentioned, it should stay silent and route updates via hooks to the owner.
3. **Tagged specialist = scoped reply only.**
   - When tagged, reply only to the tagged request (no broad channel takeover), then return to silent mode.
4. **Manager synthesis for multi-agent asks.**
   - If a user asks multiple roles at once, specialists send inputs to Manager via hooks; Manager posts one consolidated reply.
5. **Duplicate suppression window (30s).**
   - If an equivalent answer has just been posted by another agent, post only incremental/new info.