Lineage and Audit Controls

Lineage explains how data moved. Audit logs explain who touched it. Quality monitors explain whether it remained fit for purpose.

Incident evidence

During a production quality review, collect:

• upstream tables and transformations,
• users or jobs that accessed the affected asset,
• recent schema and permission changes,
• monitor results around the incident window,
• remediation decisions and owners.

Example control question

If a feature table feeds three models, can each model owner see when the table changed and who approved the change?

Operating rhythm

Lineage is not only for audits. It is a daily debugging tool when a metric moves unexpectedly.