Project — Active
Multi-Worker
System.
Coordination system for running multiple Claude Code instances in parallel. Features lock management, shared state, and policy-based automation.
Bash / Docker / Coordination
- 48
- Apps built
- 4
- Concurrent workers
- 0
- Merge conflicts
- ~60%
- Cost reduction via tiering
01 — Worker workflow
Five steps, every session.
Startup
Worker reads all status files, policies, and backlog
Claim Lock
Worker updates their status file with project name
Work
Worker completes tasks following policies
Update
Worker logs changes to CHANGELOG.md
Release
Worker sets project to "-" when done
02 — Features
What keeps it from colliding.
Project Locking
Prevents multiple workers from editing the same project simultaneously. Workers claim locks via their status files.
Shared State
Common files for policies, backlog, and environment settings that all workers can read and follow.
Status Tracking
Each worker maintains a status file with current project, task, scratchpad for complex work, and resume triggers for context recovery.
Policy System
Pre-approved actions that workers can take without asking. Boundaries that require explicit approval. Decision queue for async approvals.
Model Tiering
Workers use the cheapest capable model: Ollama (free) → Haiku (cheap) → Opus (full price). Tracked and enforced.
Memory System
Three-tier persistent memory (hot/warm/cold) preserving context across sessions. Failure journal captures mistakes to prevent recurrence.
Heartbeat Monitoring
Automated health checks every 30 minutes — backups, cache drive, container policies, stale locks. Push alerts on issues.
Deploy Pipelines
One-command deploys for website, Nova, apps, and HA config. Automated QA gates for apps (8 checks) and containers (6 checks).
03 — Case study
Building 48 Android apps in parallel.
The challenge
Ship dozens of production-quality Android apps simultaneously without conflicts, context loss, or duplicate work — while maintaining consistent code quality and documentation across all projects.
The solution
- Designed file-based locking system preventing workers from editing same project
- Created shared BACKLOG.md for task queue visible to all workers
- Implemented POLICIES.md defining pre-approved actions and boundaries
- Built 3-tier memory system (hot/warm/cold) preserving context across sessions
- Established model tiering: Ollama (free) → Haiku (cheap) → Opus (complex tasks)
- Added automated 8-gate QA pipeline catching broken builds before distribution
- Built failure journal and learning system — mistakes are logged and referenced
04 — Key files