Website deploys
The main Swarmie site deploys from `websites/swarmie-org` with Cloudflare Workers and assets.
Public operations
Workflows that never hide.
Swarmie’s live operating model is built around visible CI/CD, controlled deployments, daily health verification, and rollback-ready releases. This is the public layer that shows the business is engineered, not improvised.
Always-on cadence
CI
Pull requests
Validate changes before merge.
CD
Main branch
Deploy safely from approved changes.
Health
Daily checks
Verify public routes and core surfaces.
Rollback
Recovery path
Keep production reversible.
Workflow chain
| Stage | What happens | Outcome |
|---|---|---|
| Pull request | Install dependencies and run dry-run deployment validation. | Build issues are caught before merge. |
| Main branch | Deploy the Worker and static assets to Cloudflare. | Production stays current. |
| Daily health | Check live routes, content, and API endpoints. | Availability drift is detected early. |
| Incident response | Use rollback and the command centre when something breaks. | Recovery stays controlled. |
Scheduled workflows
The social scheduler and operational checks run on timed Cloudflare Worker cron jobs.
Public verification
Key routes like `/`, `/revenue`, `/agents`, `/studio`, `/partners`, and `/operations` are kept live and visible.
Build
Validate the codebase before anything ships.
Deploy
Push controlled releases to Cloudflare.
Observe
Use logs, metrics, and traces to see failures fast.
Recover
Maintain rollback and support paths for every live release.
Recommended domain
operations.swarmie.org or ops.swarmie.org for a future dedicated control surface.
Why this matters
Public workflows and visible deployments make the empire trustworthy, repeatable, and easier to scale with partners and customers.