Integrate independent table branches without losing their rules — what should the operator record?
Parallel work is useful when different operators own disjoint parts of a research table. Integration still needs a clear boundary: independent branches can use incompatible schemas or make conflicting assumptions about the same key. Compare contracts and membership before merging, preserving each branch's actual input revision and authorized scope.
Keep branch lineage and conflicting interpretations visible when combining local operational work.
Record branch_key, owned_fields_or_rows, input_revision and transform_revision. A branch that changes shared key semantics is not independent merely because its output lives in a separate file, so flag contract changes before accepting parallel integration assumptions.
Reconcile actual membership, schema and unresolved exceptions against the declared branches. Publish the checked candidate revision only when the integration preserves permitted lineage; branch checks alone do not establish that the combined artifact is correct or appropriately shareable.Declare branch ownership
Record branch_key, owned_fields_or_rows, input_revision and transform_revision. A branch that changes shared key semantics is not independent merely because its output lives in a separate file, so flag contract changes before accepting parallel integration assumptions.
Compare output contracts
Check column types, null handling, identity namespaces and window rules. If branches differ, propose a specific adapter or reconciliation instead of unioning their columns and allowing the receiving application to coerce mismatches into generic text cells.
Inspect overlap
List keys or fields modified by several branches and distinguish identical updates from conflicting interpretations. A repeated title is not enough to establish overlap, and equal keys still require compatible object type and source context before they can be compared.
Create an integration candidate
Name every contributing branch revision and document combination rules. Leave conflicting rows unresolved rather than choosing a branch by save time or operator preference, and keep identifying evidence within the access boundary shared by the intended integration task.
Verify integrated behavior
Reconcile actual membership, schema and unresolved exceptions against the declared branches. Publish the checked candidate revision only when the integration preserves permitted lineage; branch checks alone do not establish that the combined artifact is correct or appropriately shareable.
Keep the boundaries clear.
- Keep branch lineage and conflicting interpretations visible when combining local operational work.
- Operational record: Declare branch ownership. 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.