Files

Antoine 3289a76e19 feat: add Atomizer HQ multi-agent cluster infrastructure

- 8-agent OpenClaw cluster (Manager, Tech-Lead, Secretary, Auditor,
  Optimizer, Study-Builder, NX-Expert, Webster)
- Orchestration engine: orchestrate.py (sync delegation + handoffs)
- Workflow engine: YAML-defined multi-step pipelines
- Agent workspaces: SOUL.md, AGENTS.md, MEMORY.md per agent
- Shared skills: delegate, orchestrate, atomizer-protocols
- Capability registry (AGENTS_REGISTRY.json)
- Cluster management: cluster.sh, systemd template
- All secrets replaced with env var references

2026-02-15 21:18:18 +00:00

1.4 KiB

Raw Blame History

Hooks Protocol — Inter-Agent Communication

When You Receive a Hook Message

Messages arriving via the Hooks API (delegated tasks from other agents) are high-priority direct assignments. They appear as regular messages but come from the delegation system.

How to Recognize

Hook messages typically contain specific task instructions — e.g., "Find density of Ti-6Al-4V" or "Review the thermal analysis assumptions." They arrive outside of normal Discord conversation flow.

How to Respond

Treat as top priority — process before other pending work
Do the work — execute the requested task fully
Respond in Discord — your response is automatically routed to Discord if --deliver was set
Be thorough but concise — the requesting agent needs actionable results
If you can't complete the task, explain why clearly so the requester can reassign or adjust

Status Reporting

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

[YYYY-MM-DD HH:MM] <your-agent-name>: Completed — <brief description of what was done>

Only the Manager updates PROJECT_STATUS.md. Everyone else appends to the log.

Delegation Authority

Agent	Can Delegate To
Manager	All agents
Tech Lead	All agents except Manager
All others	Cannot delegate (request via Manager or Tech Lead)

1.4 KiB Raw Blame History