Skip to content

Glossary

The terms used in the Cortrix documentation.

These are the terms the Cortrix documentation uses. Each concept has exactly one name.

Product and positioning

TermDefinition
access pathA way for an agent or application to use Cortrix: the HTTP API, MCP, the Python SDK, framework adapters, or the built-in Agent
Agent-nativeDesigned around agent data workflows: semantic processing, memory, and traceability are concerns of the shared storage layer
built-in AgentThe fixed-flow chat service that ships in the repository
framework adapterThe cortrix-skills package, which turns Cortrix tools into each agent framework’s native format
Quick StartThe path that starts Cortrix locally with Docker and runs a first query
semantic storageA storage layer that connects information with the context an application needs to use it

Data model

TermDefinition
blockThe smallest searchable unit, derived from a document or a memory record
documentSource material uploaded to Cortrix
eventA memory type. It decays over time
factA memory type. It doesn’t decay over time
interactionOne conversation turn: the user’s question and the assistant’s answer
memoryStructured long-term information. Its type is fact, preference, or event
metadataKey-value information attached to a document, block, or memory
namespaceA logical collection boundary for documents, blocks, memory, and queries. It isn’t an authentication or tenant-security boundary
preferenceA memory type. It doesn’t decay over time
sessionA set of conversation turns grouped together
sourceThe original document a block belongs to

Ingestion

TermDefinition
batch submitSubmitting several documents in one request
chunkingSplitting text into blocks
database importImporting the rows of a database table or query into a namespace
embeddingTurning text into a vector
enrichmentUsing an LLM to add entities and summaries to ingested content
file uploadUploading one file as multipart. It returns the document identifier right away
ingestionEverything that happens to a document between upload and being searchable
inline uploadSubmitting text content directly in a JSON request body. Processing is asynchronous
parsingTurning a file into text
Semantic Processing Chain (SPC)The ingestion pipeline: parsing, chunking, enrichment, embedding, and indexing
taskOne asynchronous processing job. You can check its progress and cancel it
watcherTracks a directory and imports new files in it automatically

Retrieval

TermDefinition
candidate poolThe set of candidates fetched before reranking and truncation. It’s larger than top_k
coverage ratioThe share of requested namespaces that were queried successfully
cross-namespace queryQuerying several namespaces at once and merging the results
dense retrievalLooking up semantically similar content in the vector index
full-text searchLooking up content by keyword
fusionMerging the results of several retrieval paths into one list by rank
hybrid searchUsing several retrieval paths together and fusing their results
partial successReturning the parts that succeeded when some sub-operations fail, with the failures described in meta
queryA retrieval request over one or more namespaces
rerank scoreThe relevance score given by the reranker model
rerankingScoring each candidate with a cross-encoder model and reordering them
sparse retrievalLooking up content with sparse vectors

Memory operations

TermDefinition
invalidationMarking a memory as no longer valid while keeping the record
memory extractionExtracting memories from conversations automatically
soft deleteMarking something deleted while keeping it restorable or traceable, without physically removing it

Deployment and runtime

TermDefinition
admin endpointA management interface that accepts loopback requests only
execution providerThe backend that runs a model: CPU, CoreML, or CUDA
garbage collectionThe background process that removes deleted data in stages
LLM roleOne use of an LLM, configured separately. There are five: semantic_llm, vision_llm, agent_llm, doc_summary_llm, and enricher_llm
local modelThe embedding and reranking models that run on your machine and need no external service
loopback addressA network address reachable only from the same machine
model manifestThe file that records each model file’s source, size, and checksum
readiness checkThe health check that confirms the API, the models, and the data are all available
volumeThe Docker storage that holds persistent data

Interfaces

TermDefinition
authenticationConfirming who the caller is
error categoryThe classification of an error: auth, quota, transient, timeout, or permanent
structured errorAn error response that carries code, retryable, category, and retry_after_ms
tenantOne unit of isolation in the multi-tenant model
toolA callable operation that the MCP server or the framework adapters offer to an agent
traceThe record a call leaves on the server, which can be queried by session

Status labels

TermDefinition
In developmentPresent in part or being built. Not supported yet
PreviewAvailable and documented. Cortrix is in pre-release, so verify it in your own environment before production use