Trace a derived table back through its permitted inputs — what should the operator record?
A released table can pass through projection, filtering, joining and sorting before anyone asks where a row came from. Capture each operation as a link between artifact revisions. This makes reconstruction practical without duplicating every response or claiming that a later retrieval will reproduce the same original records.
Build a minimal lineage chain for a table that combines several local operations.
Create output_revision, input_revisions, operation_type and rule_revision fields. A join can have several inputs, while a sort ordinarily has one; the lineage representation must express that difference without inventing a single parent where several were actually used.
Attach the checked chain revision and unresolved edges to the artifact. If retention prevents reopening an older input, record that limitation rather than rebuilding it from memory or maintaining a forbidden copy solely to satisfy a reproducibility claim.Inventory operation links
Create output_revision, input_revisions, operation_type and rule_revision fields. A join can have several inputs, while a sort ordinarily has one; the lineage representation must express that difference without inventing a single parent where several were actually used.
Check reverse navigation
Pick an authorized output row and follow its key through each operation to the original receipt reference. If the key was expanded or transformed, require an explicit mapping instead of relying on matching display titles across intermediate files.
Test a broken edge
Use a labeled fixture whose filter output points to a missing input revision. The lineage validator should report unresolved-parent and block a complete-provenance signoff, even if the final table itself parses and appears visually plausible.
Minimize lineage disclosure
Keep operation metadata and permitted row references in the lineage index. Avoid copying restricted excerpts or account labels into every node name, because a widely shared dependency map can otherwise become another identifying evidence store.
Release with limits
Attach the checked chain revision and unresolved edges to the artifact. If retention prevents reopening an older input, record that limitation rather than rebuilding it from memory or maintaining a forbidden copy solely to satisfy a reproducibility claim.
Keep the boundaries clear.
- Build a minimal lineage chain for a table that combines several local operations.
- Operational record: Inventory operation links. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.