Antoine
3289a76e19
- 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
📁 Atomizer Projects Directory
Shared project files — all agents read from here, all work flows through here.
Structure
projects/
├── <client>-<job>/ # One folder per project
│ ├── 0_intake/ # CEO drops files here: contracts, requirements, CAD screenshots, notes
│ ├── 1_breakdown/ # Technical Lead's analysis (OP_01 output)
│ ├── 2_study/ # Study Builder's code, config, AtomizerSpec
│ ├── 3_results/ # Post-Processor's analysis, plots, data
│ └── 4_deliverables/ # Reporter's final output (PDF reports, client-ready)
├── .template/ # Empty template — copy for new projects
└── README.md # This file
Conventions
- Folder naming:
<client>-<job>in lowercase kebab-case (e.g.,starspec-wfe-opt,acme-bracket-topo) - Slack channel: matches the folder name:
#starspec-wfe-opt - Intake files: anything goes — PDFs, images, text notes, CAD exports, screenshots, voice memos
- Each phase folder: the owning agent writes a README.md summarizing what's inside
Workflow
- CEO creates folder + drops files in
0_intake/ - CEO creates matching Slack channel + posts "new project, files ready"
- Manager assigns Technical Lead to break it down
- Work flows through numbered folders as the project progresses
- Final deliverables land in
4_deliverables/for CEO review
Access
All agents have read access to all projects. Agents write only to their designated phase folder.
Created: 2026-02-08 by Manager 🎯