Auditability proof surface
Data Lineage Architecture
Shows source-to-replay traceability for every governed finance decision: source, version, timestamp, policy, evidence, action, and outcome.
Lineage path
01
SAP Invoice
Source record, source system, document ID, company code, and timestamp.
v
02
Databricks
Data product, table/version, quality score, certification, and refresh time.
v
03
Context Runtime
Supplier, PO, contract, cost center, approver, policy, and ontology relationships.
v
04
Decision
Agent, recommendation, confidence, alternatives, and approval path.
v
05
Evidence Pack
Source records, documents, policies, prior decisions, and approvals.
v
06
Replay
Immutable reconstruction with inputs, policy, evidence, reasoning, action, and outcome.
Lineage questions answered
| Question | Runtime answer |
|---|---|
| Which data? | Every decision records source records, data products, document IDs, and evidence pack IDs. |
| Which version? | Dataset/table version, source record version, policy version, prompt/model version, and document version. |
| Which timestamp? | Source timestamp, ingestion timestamp, context snapshot timestamp, policy evaluation time, and approval time. |
| Which policy? | Policy ID, owner, version, evaluation result, violation/escalation, and override reason where applicable. |
| Can it replay? | Replay stores signal, context, policy, evidence, recommendation, human action, action gateway, outcome, and learning. |
Audit payload
Source referencesDataset versionsPolicy versionEvidence packAgent identityTool callsHuman approvalOutcomeReplay ID
Workshop answer
Data lineage is not a separate after-the-fact report. It is captured during decision formation and becomes part of evidence, replay, audit, incident response, and learning.
Proof links
Data Access Strategy
Data Trust Explorer
Evidence Vault
Runtime Topology