Memory architecture
Flock memory is the coordination substrate plus durable episode artifacts — not a vector store or chat transcript archive.
Layers
| Layer | Where | Role |
|---|---|---|
| Hot | In-process blackboard + pheromone field | Live stigmergy (decay, wake, dispatch) |
| Warm | .flock/ JSON today; .flock/memory.db planned | Episodes, traces, checkpoints, topology archive |
| Cold | Turso Sync (optional, Phase 3) | Team backup and multi-machine share |
Today (Phase 0)
flock run --goal "reach target" --plugin gridworld # → .flock/episodes/<id>.json
flock replay --episode .flock/episodes/<id>.json
flock replay --continue-run --episode .flock/episodes/<id>.json
Working state: flock_read_blackboard, flock_deposit_signal during live episodes (MCP tools).
Planned
Phase 1 adds flock-memory, MCP flock_recall / flock_remember / flock_query_field_history, and optional SQLite backend with JSON mirror.
What never goes in the database
- Live pheromone ticks (stay in-process)
- Conversation transcripts for coordination
- Vector embeddings (deferred)
See Coordination model for the coordination protocol.