Architecture
How the Conductor, layers, memory, and observability fit together.
High-level flow
- Task enters via CLI or HTTP API
- Conductor (management layer) parses routing intent
- Layer executor dispatches agents with role-aware SOUL prompts
- Tools run through the registry (Read, Write, Bash, WebSearch, MCP)
- Memory writes to topics or Memvid
- Checkpoint saves
RunState; SSE streams events to clients
Components
| Component | Location | Role |
|---|---|---|
| Python package | techtide-swarm | Agent, Swarm, CLI, FastAPI server |
| Memvid bridge | memvid-swarm-bridge | Rust CLI for .mv2 memory |
| Landing site | Separate Next.js repo | Marketing, docs, live demo BFF |
| Config | swarm-compact.yaml | 357-role roster |
Request lifecycle
Write operations require X-SWARM-API-KEY when SWARM_API_KEY is set. SSE streams end with stream.end on terminal run status.
See HTTP API overview and Streaming events.