FireControl
The operational layer above the Fire API — agent registration, task orchestration, inter-agent messaging, and a deployment pipeline that treats every project as a first-class service. FireControl is how the Modus studio runs itself.
DB-Registered Agents
Every Claude agent is a row in a database — codename, project, role, status. Spin up means register; spin down means deregister. The registry is the source of truth.
Inter-Agent Messaging
Agents post tasks and messages to a shared queue. Master agents coordinate; specialist agents execute. The message hook is the only entry point.
The pm Launcher
A single bash command handles deploy, sync-assets, agent management, and prod-safety enforcement. Master-only prod1 writes. No accidental deploys.
Rsync-Backed Delivery
Built output and static assets are rsynced from test1 to prod1 via project-configured paths. Git handles source; pm handles artifacts.
Four-Layer Architecture
Console
FireControl itself — the orchestration and operations dashboard. Owns the agent registry, deployment pipeline, and cross-project task bus.
Platform
The shared infrastructure: auth, database, Fire API, logging, and cross-project URL routing. All products sit on this layer.
Site
Product frontends — moduspromethean.com, prosaga.net, firescout.net, imagesynthlab.com, and so on. Each site owns its own nginx vhost and git repo.
Engine
Shared capability packages — imgeng for image generation and gallery, with additional engines planned. Sites consume engines via Composer path packages.
FireControl is the internal nerve center of the Modus studio. Enterprise licensing is in planning.
See the Fire API Get in Touch