Track parent and child versions of research tables — what should the operator record?
Two tables named final can represent entirely different evidence. Parent links make revisions intelligible without relying on filenames. Start with returned records and distinguish a new retrieval from a corrected local transformation, because each operation changes a different part of the lineage.
Use explicit parent links to distinguish a revised table from a fresh retrieval or an unrelated branch.
Create table_revision and parent_revision fields; a first revision has no parent, while a derived table names its actual input revision. A locally filtered revision can name r1 as parent while a new retrieval names a separate receipt; these are not interchangeable ancestry relationships.
Replace final-final filenames with manifest references and point collaborators toward one approved revision without deleting unresolved branches outside your authority. A registry pointer such as approved_revision r4 is clearer than renaming every predecessor obsolete, especially while a competing branch still awaits review.Define revision identity
Create table_revision and parent_revision fields; a first revision has no parent, while a derived table names its actual input revision. A locally filtered revision can name r1 as parent while a new retrieval names a separate receipt; these are not interchangeable ancestry relationships.
Label the operation
Use local operation values such as filter, rename-column or authorized-refresh and explain why a new child revision was necessary. A useful log entry is r2, parent r1, operation filter, rule has-original-link; another operator should be able to reproduce that exact selection.
Follow the branch
For a competing filter experiment, create a sibling revision rather than rewriting the parent. Preserve its distinct inclusion rule and owner. If r2 narrows by date and r3 narrows by format, keep their parents unchanged until a deliberately combined r4 is created and checked.
Compare sibling outputs
Inspect membership and column definitions for both branches; different row orders alone must not be reported as new source evidence. A membership diff should list left-only and right-only keys as well as shared keys whose values changed, rather than only reporting net size.
Retire ambiguous names
Replace final-final filenames with manifest references and point collaborators toward one approved revision without deleting unresolved branches outside your authority. A registry pointer such as approved_revision r4 is clearer than renaming every predecessor obsolete, especially while a competing branch still awaits review.
Keep the boundaries clear.
- Use explicit parent links to distinguish a revised table from a fresh retrieval or an unrelated branch.
- Operational record: Define revision identity. 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.