System design
A control plane for memory
CoreCortex separates authored intent, durable source state, derived indexes, query policy, and measurement.
Five layers
| Layer | Owns |
|---|---|
| Configuration | Corpus intent and immutable revisions |
| Lifecycle | Records, fragments, relations, jobs, deletion |
| Storage | Pluggable lexical, vector, relational, or graph indexes |
| Retrieval | Plans, fusion, filters, ranking, evidence contracts |
| Evaluation | Golden examples, metrics, experiment history |
Pluggable storage
CoreCortex treats storage as a strategy selected for a corpus, not as the identity of the product. Different domains may need lexical, vector, graph, relational, or hybrid retrieval, and each choice should be measured.
Graph relationships
Relations are first-class in the canonical model, so a corpus can add graph traversal when evaluation shows that multi-hop connections improve retrieval. Graph storage is a strategy, not a default requirement.
Trust boundaries
Tenant scope, access policy, provenance, and deletion propagation cross every layer. The repository includes the current security baseline and architecture decisions behind those boundaries.
Continue readingWhat is open source?→