Detect concurrent edits to a research working table — what should the operator record?
Two operators can independently correct the same table and overwrite each other's work. A baseline check makes that conflict explicit before either candidate becomes the approved artifact. Treat the conflict as a revision reconciliation task, not a reason to merge all cells automatically or choose whichever file was saved most recently.
Compare baseline revisions before accepting a candidate produced by another operator.
Attach base_revision, candidate_revision and operator_role to every proposed change. A candidate without a known baseline cannot safely claim it preserves another operator's accepted corrections, even if both files currently contain the same number of rows.
Rerun affected schema, membership and provenance checks before acceptance. Preserve unresolved conflicts and avoid calling the merge complete merely because the file opens without syntax errors or because both operators agreed that their original edits were useful.Record each starting revision
Attach base_revision, candidate_revision and operator_role to every proposed change. A candidate without a known baseline cannot safely claim it preserves another operator's accepted corrections, even if both files currently contain the same number of rows.
Detect a changed baseline
Compare the approved pointer with base_revision before acceptance. A mismatch should create concurrent-edit rather than an automatic overwrite, retaining the two candidate references for authorized review without forcing either one to become current immediately.
Classify change overlap
Compare affected row keys and columns, distinguishing disjoint edits from competing changes to the same field. Identical row counts or matching filenames provide no evidence that the edits are compatible or that neither operator changed inclusion rules.
Reconcile explicitly
For disjoint changes, create a new candidate naming both inputs and document the combination. For conflicting values, require supported evidence and an accountable choice instead of accepting the later local save timestamp as a proxy for factual correctness.
Validate the merged candidate
Rerun affected schema, membership and provenance checks before acceptance. Preserve unresolved conflicts and avoid calling the merge complete merely because the file opens without syntax errors or because both operators agreed that their original edits were useful.
Keep the boundaries clear.
- Compare baseline revisions before accepting a candidate produced by another operator.
- Operational record: Record each starting revision. 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.