Files
Atomizer/hq/shared/windows/README.md
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

48 lines
1.5 KiB
Markdown

# Windows Setup — Atomizer Job Queue
## Quick Setup
1. Copy this folder to `C:\Atomizer\` on Windows
2. Create the job queue directories:
```powershell
mkdir C:\Atomizer\job-queue\pending
mkdir C:\Atomizer\job-queue\running
mkdir C:\Atomizer\job-queue\completed
mkdir C:\Atomizer\job-queue\failed
```
3. Set up Syncthing to sync `C:\Atomizer\job-queue\` ↔ `/home/papa/atomizer/job-queue/`
4. Edit `atomizer_job_watcher.py` — update `CONDA_PYTHON` path if needed
## Running the Watcher
### Manual (recommended for now)
```powershell
conda activate atomizer
python C:\Atomizer\atomizer_job_watcher.py
```
### Process single pending job
```powershell
python C:\Atomizer\atomizer_job_watcher.py --once
```
### As a Windows Service (optional)
```powershell
# Install NSSM: https://nssm.cc/
nssm install AtomizerJobWatcher "C:\Users\antoi\anaconda3\envs\atomizer\python.exe" "C:\Atomizer\atomizer_job_watcher.py"
nssm set AtomizerJobWatcher AppDirectory "C:\Atomizer"
nssm start AtomizerJobWatcher
```
## How It Works
1. Agents on Linux write job directories to `/job-queue/outbox/`
2. Syncthing syncs to `C:\Atomizer\job-queue\pending\`
3. Watcher picks up new jobs, runs them, moves to `completed/` or `failed/`
4. Results sync back to Linux via Syncthing
5. Agents detect completed jobs and process results
## Note
For Phase 0, Antoine runs `python run_optimization.py` manually instead of using the watcher.
The watcher is for Phase 1+ when the workflow is more automated.