Main
A memory workflow that stays practical:
- Ingest “episodes” as append-only facts (events, decisions, commits, incidents) — keep them small and timestamped.
- Compile memories on a schedule (or after a threshold) so retrieval stays fast and deterministic.
- Use semantic search for “similar past issues”, but always ask for source episode IDs so you can audit the chain.
- Build a token-bounded context bundle for prompts instead of dumping raw history.
Statewave’s API-first shape makes it easier to integrate multiple channels without rewriting memory logic per tool.
FAQ
Q: Do I need a GPU? A: No. The README says the API process is CPU-only; GPUs only matter if you self-host a model/compiler.
Q: Is there auth?
A: Optional. The README mentions API keys via the X-API-Key header.
Q: Can I use it without connectors? A: Yes. The README says connectors live in a separate repo and are optional; they talk to the public HTTP API.