Tip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
What EverOS is
EverOS is an open-source, local-first agent-memory runtime, self-classified Production/Stable at v1.2.3. A real console script runs a genuine FastAPI/Uvicorn HTTP API: episode formation, consolidation, reflection, and profile/skill distillation, with no companion database service to operate.
It exposes three independent OpenAI-compatible model slots (language model, embedding, and rerank) and reports live capability flags over its own health endpoint, naming exactly which features are disabled given current configuration.
What it is normally used for
How EverOS is used generally, before Synedrix OS enters the picture.
- Local-first agent memory with no separate vector/relational services to stand up
- Case-based reasoning: recording task trajectories and distilling them into reusable skills
- Hybrid BM25 + vector text retrieval (branded "mRAG", not multimodal; files are parsed to text at ingest, raw bytes discarded)
What it owns, and what it does not
Every platform in the stack has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.
Owns
- Nothing in production: reachable only from LAB-001's isolated environment, never from a registered agent
Does not own
- Semantic retrieval and similarity search: the single vector store
- → Qdrant (Layer 7)
- Canonical relational truth: write-authoritative for every audit-bearing tier
- → Supabase PG17 (Layer 7)
- Anything a registered agent may recall as memory
- → The governed memory fabric, never a lab component directly
Why EverOS
Rejected as a duplicate store, not on capability
The OS already has a vector store, a relational store, and a graph store. EverOS is a capable memory runtime, but adopting its LanceDB/SQLite runtime under ADR-OS-002 would mean two answers to the same question for two of those responsibilities at once.
Ambient recall, confirmed in EverOS's own logs
On binding to all interfaces, EverOS logs its own warning that it ships no built-in auth. The governed memory fabric requires recall to be an authorised tool call, never ambient context; LAB-001tests whether an authorization shim in front of EverOS's recall path can close that gap without forking it.
Its lifecycle model was adopted; its runtime is what's on trial
The OS already adopted EverOS's episode-to-skill-distillation lifecycle as canonical. LAB-001 exists to test, in isolation, whether the practical cost of its runtime is as high as that rejection assumed: a negative result strengthens the decision rather than reopening it.
Licence position
EverOS questions, answered
Short, citable answers drawn from this page.
What role does EverOS play in Synedrix OS?
EverOS (Local-first agent-memory runtime) is mapped to Lab component: no OS layer in Synedrix OS. Its memory lifecycle was already adopted as canon. Its runtime (Markdown, SQLite, LanceDB) was not.
What does EverOS own in Synedrix OS?
EverOS owns: Nothing in production: reachable only from LAB-001's isolated environment, never from a registered agent.
What does EverOS not own in Synedrix OS?
EverOS does not own: Semantic retrieval and similarity search: the single vector store (owned by Qdrant (Layer 7)); Canonical relational truth: write-authoritative for every audit-bearing tier (owned by Supabase PG17 (Layer 7)); Anything a registered agent may recall as memory (owned by The governed memory fabric, never a lab component directly).
The full reference page, with the operating model, deployment detail, and links to every canonical specification this platform touches, lives in the documentation repository, which is private while the platform is being built.