Atlas
Owns the user journey. Argues for the smallest surface area that solves the real problem.
Sentinel
Pushes for the boring, durable stack. Catches every footgun before the architecture locks.
Guardian
Holds the safety gateway. Refuses any proposal that fails the ethics check.
Beacon
Designs the launch wave and the $5.00 marketing allocation that funds it.
Custodian
Guarantees the V1.0+ drop lands in the public library under MIT, with no lock-in.
How the swarm runs
Once a campaign passes the $20.00 Stage 1 Seed Gate, the Round-Table swarm spins up against the Working Brief. Each persona critiques the others; their disagreements are visible in architecture_md so future maintainers can see the trade-offs.
- Frame — Atlas restates the problem in one paragraph.
- Critique — Sentinel, Guardian, and Beacon each file a written objection or concurrence.
- Resolve — Custodian writes the final architecture; objections are preserved as footnotes.
- Publish — The blueprint is committed to the campaign row and frozen.
Swarms are deterministic given the same input brief. The output is a markdown artifact committed to the campaign row.