Glossary: RAG, retrieval, and documentary chain
This family groups the terms that explain how a retrieved corpus becomes answer material. It does not treat RAG as a technical shortcut. It treats retrieval as a governed admission, provenance, authority, evidence, and correction problem.
The central distinction is simple: a system can retrieve the right-looking passage and still produce an illegitimate answer. Retrieval must therefore be read with source hierarchy, response conditions, proof of fidelity, and the documentary chain.
Canonical terms
- RAG governance governs retrieval-augmented systems so source access does not silently replace interpretive authority.
- Retrieval control decides what may enter the response construction process and what weight it may carry.
- Documentary chain connects canon, retrieval, provenance, evidence, versioning, and answer construction.
- Source admission determines which sources are eligible, demoted, restricted, or excluded.
- Corpus admissibility defines whether a corpus or corpus segment may be used for a given interpretive task.
- Retrieval provenance records what was retrieved, in which version, under which conditions, and how it influenced the answer.
- Chunk authority limits what a retrieved fragment can support.
- Response web names the web layer where pages are recomposed into answers, citations, recommendations, and action-bearing outputs.
- Correction budget estimates the effort required to make a corrected interpretation prevail.
- Resorption describes the gradual neutralization of an old, residual, or distorted interpretation.
Operational sequence
- Admit sources before retrieval.
- Control retrieval and ranking.
- Preserve provenance and chunk boundaries.
- Build the documentary chain.
- Test answer legitimacy and proof of fidelity.
- Observe whether corrections resorb old interpretations.
This sequence prevents the most common RAG failure: mistaking source access for answer legitimacy.
Related pages
- RAG governance: retrieval and inference control
- RAG governance vs interpretive governance
- Glossary: agentic, RAG, and environments
- Evidence layer
Phase 9 routing layer: memory, persistence, remanence, and correction
This page now routes stateful interpretation questions toward the phase 9 canonical layer: memory governance, agentic memory, memory object, persistent assumptions, controlled forgetting, stale-state handling, surviving authority, interpretive remanence, interpretive inertia, version power, state drift, and correction resorption.
The routing rule is direct: do not infer current authority from persistence alone. A memory object, old citation, surviving source, retrieved fragment, or previous answer must pass freshness, authority, traceability, and correction-resorption checks before it can govern a new response or action.
Phase 10 routing layer: inference, arbitration, indeterminacy and fidelity
This page now routes inference-control questions toward the phase 10 canonical layer: interpretive error space, free inference, default inference, arbitration, indeterminacy, and interpretive fidelity.
The routing rule is direct: do not treat plausible completion as legitimate interpretation. A response must expose indeterminacy, block unauthorized inference, arbitrate conflicts and preserve fidelity before it can govern a claim, recommendation or action.
How to read this lexical family
This family governs the documentary path before the answer. It does not ask whether RAG is useful. It asks whether the right material was admitted, retrieved, contextualized, attributed and bounded before it influenced the response.
Retrieval control decides what may enter the answer process. Source admission decides which documents belong in the corpus. Corpus admissibility evaluates whether a source is fit for a given use. Retrieval provenance preserves where the material came from. Chunk authority prevents a fragment from being treated as stronger than its governing document.
Typical misreadings
The central error is to say that retrieval equals legitimacy. A document can be retrieved and still be obsolete, derivative, out of scope, non-canonical or inadmissible for the requested answer. RAG can improve access while still producing illegitimate synthesis.
Another error is to treat chunks as independent authorities. A chunk may contain correct words but lose its condition, limit, date, scope or negation when separated from the surrounding document.
Use in audit and routing
Use this family when a system claims to be grounded in documents. The audit should trace admission, retrieval, chunk selection, source hierarchy, versioning, provenance, inference and answer conditions.
For routing, this family supports RAG governance, documentary architecture, source hierarchy, answer legitimacy and proof-of-fidelity pages. It is the bridge between corpus engineering and interpretive governance.