Core data model

Concepts

Use this glossary for the data, processing, search, model, evaluation, and operating terms used throughout CoreCortex.

Corpus and source data

TermMeaning
CorpusA corpus is a collection of documents, records, audio, images, or other information about a subject. CoreCortex prepares it for search, keeps results linked to their sources, and tests retrieval with reviewed questions.
DatasetOne coherent part of a corpus, such as a document archive, database export, or recording series
SourceThe system, file collection, feed, or export from which a dataset was obtained
SnapshotThe exact source contents processed in one reproducible run
ModalityThe form of source information: text, structured data, audio, video, image, or another media type
Source identityThe stable identifier that connects a CoreCortex record to the item in its source
RecordThe normalized representation of one source item inside a dataset
AttributeA typed field on a record used for meaning, filtering, policy, or display

Representations and derived data

TermMeaning
Normalized recordA record in the stable CoreCortex shape, with identity, content, attributes, access, and source details
FragmentA retrievable unit derived from a record; the documentation also calls this a passage when it contains text
ChunkThe source span or content selection used to create a fragment
ProcessorVersioned code that converts, enriches, chunks, embeds, or extracts information
ProvenanceThe source, processor, settings, and timestamps that explain how an object was produced
RelationA typed, directed connection between records or fragments, with its own source evidence
Access policyThe principals or rules that determine who may retrieve a record and its derived data
Canonical dataRecords and reviewed judgments kept independently from any search or graph backend

Search and storage

TermMeaning
SchemaThe fields, types, identities, and constraints expected at a particular boundary
Field roleHow a field is used in search: lexical text, vector, exact filter, relation, or returned content
IndexSelected corpus data arranged for fast lookup or ranking
ProjectionA rebuildable copy of canonical data in a search, relational, vector, or graph backend
BackendThe storage or search system that holds a projection
AdapterThe CoreCortex implementation that translates a common operation to a backend
EmbeddingA numeric representation used to compare semantic similarity
Lexical searchSearch that ranks words, terms, identifiers, and phrases, commonly with BM25

Queries and retrieval

TermMeaning
QueryThe question or lookup request sent to retrieval
Retrieval planThe named configuration that chooses indexes, candidate methods, filters, ranking, and result limits
CandidateA record or fragment returned by one first-stage search method before final ranking
FilterAn exact condition that removes results outside scope, time, category, tenant, or access policy
RankingThe ordering of matching candidates by a score or policy
FusionA method that combines candidate lists; reciprocal rank fusion, or RRF, combines their rank positions
Top KThe number of highest-ranked results retained or sent to the next step
RerankerA second-stage scorer that reorders a smaller candidate set
Graph-assisted retrievalA bounded traversal of evidenced relations followed by retrieval of the linked source content
TraceThe recorded plans, index versions, scores, filters, and identities used for one request

Models and processors

TermMeaning
StrategyA registered implementation selected through a stable CoreCortex interface
Chunking strategyThe rules that create fragments from normalized record content
Embedding providerAn implementation that creates vectors and records the model identity and revision
Language-model providerAn implementation that sends authorized evidence to a selected language model
Relation extractorAn implementation that produces evidenced triples or typed relations
Response planThe configuration for evidence limits, model invocation, citation requirements, and abstention
SynthesisThe optional step that uses retrieved evidence to produce an answer or other model output
Evidence envelopeThe authorized fragments supplied to a model for one response
CitationA reference from generated output to a fragment inside its evidence envelope
AbstentionAn explicit response stating that the available evidence cannot support an answer

Evaluation

TermMeaning
Reviewed judgmentA question plus the records or fragments that a subject-matter reviewer accepts as relevant
Golden dataThe versioned set of reviewed judgments used to compare configurations
Hard negativeA plausible result that a reviewer has marked irrelevant for a specific question
Expected-empty queryA question designed to return no supported result
Retrieval evaluationMeasurement of whether reviewed evidence appears and where it ranks
Generation evaluationMeasurement of required facts, citation support, faithfulness, and abstention
Hit@KThe share of questions with an accepted result among the first K results
MRRMean reciprocal rank; a score that rewards placing the first accepted result near the top
NDCGNormalized discounted cumulative gain; a rank score that can use graded relevance
FaithfulnessWhether generated claims are supported by the supplied evidence
MissA query or answer that fails a reviewed expectation and needs analysis

Runs and promotion

TermMeaning
ConfigurationThe declared datasets, processing steps, storage, indexes, retrieval plans, and optional response plans
Configuration revisionAn immutable saved version of a configuration
Configuration fingerprintA SHA-256 identifier for the exact settings used in a run
Ingestion batchA validated set of records and operations prepared for one apply step
ReceiptMachine-readable evidence that a batch or projection operation ran against named inputs and settings
A–E retrieval experimentsOrdered comparisons of representation, chunking, embeddings, retrieval, and full evaluation
GateA required quality, policy, integrity, latency, or cost condition
Certification manifestThe final status and evidence that show whether a selected corpus configuration is ready for pipelines

Read the detailed guides

The glossary defines the terms. The guides below explain how to configure and use them.

Continue readingIndexes and schema→