Introduction
What Swarm 357 is, who it is for, and how the 357-role catalog works.
Swarm 357 is a 357-role catalog plus orchestration runtime for Claude agents across six business layers: Sales, Support, Marketing, SEO, Research, and Operations, plus Management meta-agents.
It is an organizational ontology for agents. It is not 357 simultaneous Opus sessions.
What you get
- Layered specialists with YAML roster and SOUL templates for each role
- Portable memory via flat-file topics and optional Memvid
.mv2bridge - Honest cost controls with layer budgets and logged model downgrade at 80% spend
- Production security defaults: Bash policy gate, filesystem confinement, HITL approvals
- Observable runs with checkpoints, SSE events, and local JSONL traces
Who it is for
- Teams running Claude Code or API agents who need structure, not chaos
- Operators who want FinOps and security reviewers to verify claims
- Builders who prefer open-core (Apache-2.0) over black-box platforms
Next steps
- Quickstart to run your first task in five minutes
- Architecture for the system diagram
- Status and maturity for honest feature labels