Lab components
Reference material for components under evaluation in the governed lab lane — not part of the Synedrix OS tech stack, not counted among the twelve platforms, and not citable as authority by any canonical document.
What a lab component is. A lab component is real, third-party software running under a time-boxed evaluation charter, in structural isolation from every production system: its own network, its own datastores, no write path into
synedrix_core,postgres-core,redis-bus,qdrant-core, orneo4j-core. Nothing it produces is a durable memory record, an audited action, or a production write. A charter’s only two outcomes at expiry are promotion — via a normal ADR — or retirement. There is no third, indefinite state.
This page exists so a reader encountering LanceDB or SQLite named elsewhere in this documentation set — most often as the reason something was not adopted — has somewhere to click through to, without that click implying the component is part of the platform.
Active lab charters
| Lab | Component | Question | Status | Expires |
|---|---|---|---|---|
LAB-001 | EverOS | Derisk the OS’s own memory-lifecycle build; establish an EverMemBench baseline; test whether substrate duplication and ambient recall are as costly as ADR-OS-002 argues; spike Case → Skill distillation | open | February 2027 |
LAB-002 | Semantica | Whether Docling-based structural parsing improves retrieval over the existing chunker, run as a parallel, additive Qdrant collection; test PROV-O export for os-agt-008 | open | February 2027 |
LAB-003 | Laya and Jev (System One decision models) | Whether a decision model, behind the existing custom-router-ref routing seam, removes LLM calls at equal quality; whether self-hostable Laya reaches parity with managed Jev | open | April 2027 |
Full evidence, isolation contracts, and pre-registered exit criteria are in the charters themselves. This page and the component pages below carry only descriptive, licence, and boundary information — the charters are the governance record.
Lab component pages
The components under active evaluation, each under its charter:
| # | Component | Evaluated under | Role |
|---|---|---|---|
| 1 | EverOS | LAB-001 | Local-first agent-memory runtime |
| 2 | Semantica | LAB-002 | GraphRAG / knowledge-graph toolkit |
| 3 | Laya | LAB-003 | System One decision model, self-hosted |
| 4 | Jev | LAB-003 | System One decision model, managed API |
Their substrates, described separately because each is also named as the specific reason something was not adopted, elsewhere in this documentation set:
| # | Component | Substrate of | Role |
|---|---|---|---|
| 5 | LanceDB | EverOS (LAB-001) | Embedded vector index |
| 6 | SQLite | EverOS (LAB-001) | Embedded relational state |
| 7 | Docling | Semantica (LAB-002) | Structural document parsing |
Why these pages are not in “The twelve platforms”
Platform reference index enumerates the twelve canonical platforms, ordered by canonical/architecture.yaml, plus one conditional component (Ollama/vLLM) explicitly marked as not counted among the twelve. This page follows the same pattern one level further: lab components are neither in the twelve nor conditional — they are outside the tech stack entirely, described here only because they are named, in plain text with no page to point to, across several canonical documents (Tech Stack §“Libraries adopted”, Memory Fabric Spec §12, Qdrant §“The single vector substrate”) as the specific reason EverOS’s runtime was rejected from canon.
Synedrix OS · Platform reference · Lab · index