> ## Documentation Index > Fetch the complete documentation index at: https://docs.gable.ai/llms.txt > Use this file to discover all available pages before exploring further. # Generating Compliance Evidence > Use lineage to answer where regulated data comes from, what computes it, and who consumes it Compliance reviews start from a question about data, not a question about code: *where does this regulated output come from, what computed it, and which systems consume it?* Because Gable's lineage is derived from your services' actual source code — not from documentation or manually maintained diagrams — it can answer those questions with evidence that reflects how the software really behaves. This page describes the workflow for assembling that evidence. ## Trace the regulated data 1. Open the **Lineage Explorer** and search for the regulated or sensitive field — for example, an output field of a report, feed, or API response. 2. Select the field to filter the graph to its lineage. 3. Trace **upstream** to confirm every source that feeds the field: which services touch it, which data stores hold it, and where it originally enters your systems. 4. Trace **downstream** to identify every consumer that depends on it. Tracing a sensitive field upstream across services See [Tracing Data Lineage](/docs/tracing/end-to-end-lineage) for the full tracing workflow. ## Show how the data is computed For each service along the path, open **Component Details** to show what happens to the data inside the service: * the path connecting the relevant ingress and egress * the field mappings along that path * the field data flow — the steps the value takes through the code This answers "what computed this value?" at the level of specific services and fields, backed by the analyzed code version. ## Export the evidence Capture the trace as an artifact for the review: * **CSV export** — with the field selected in the Lineage Explorer, use **Export CSV** to download the upstream lineage paths for the field, hop by hop. See [Exporting Lineage](/docs/tracing/exporting-lineage). * **API export** — for the complete lineage of a run (components, schemas, and edges), use the [Lineage Export API](/docs/tracing/exporting-lineage#export-lineage-via-the-api). ## Anchor the evidence to a point in time Every version of a component's lineage is tied to an analysis run of a specific commit: * The **Scan Log** records every analyzed version, with its branch, commit, and analysis timestamps — a durable record of when each version of the lineage was produced and from what code. * To show how data handling changed between two audits or releases, compare the corresponding versions — see [Comparing Lineage Versions](/docs/impact/comparing-lineage-versions). The Scan Log as a point-in-time record of analyzed versions ## Coming soon Two upcoming capabilities will streamline this workflow: * [Sensitive Data](/docs/tracing/sensitive-data-classification) — start from a classification (such as PII) instead of a known field name, and track classified data across the graph. * [Approvals](/docs/impact/approvals) — sign off on a lineage version to establish the reviewed baseline your evidence is generated from.