> ## Documentation Index
> Fetch the complete documentation index at: https://project-brain.rocheaiops.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Data lineage

> How user statements, corrections, documents, citations, rebuilds, and restores retain traceability.

<a href="/assets/visuals/teach-recall-correct.svg" target="_blank" rel="noreferrer" aria-label="Open full-size diagram: Teach, recall, correct"><img src="https://mintcdn.com/roche-ai-ops/zV65QLx2v4-e7KNO/assets/visuals/teach-recall-correct.svg?fit=max&auto=format&n=zV65QLx2v4-e7KNO&q=85&s=f358f5f2c3c0410a5a1773f4df279e93" alt="Teach, recall, correct" noZoom width="1440" height="730" data-path="assets/visuals/teach-recall-correct.svg" /><span className="sr-only">Open full-size diagram: Teach, recall, correct</span></a>

A user statement produces an attributed event and may support a learning record. A correction creates a successor and preserves the earlier record as superseded. A document produces a versioned original artifact, normalized representation, chunks, derived embeddings, and retrieval citations. A rebuild replaces only derived chunks/vectors from the normalized representation.

An isolated backup restore validates an active learning record, preserved superseded history where requested, and a document checksum present in both restored PostgreSQL and the archived original. That is recovery lineage, not a substitute for the source lineage. See [provenance and lineage](/concepts/provenance-and-lineage).
