Stage a derived table before replacing the approved artifact — what should the operator record?
Writing directly over the approved file can leave a half-written table if a process stops. Stage a candidate under a distinct local revision and validate it before updating the approved reference. This operational pattern protects the accepted artifact without implying transactional guarantees from the remote research service or source platform.
Validate a candidate output separately so interrupted writes do not corrupt the accepted table.
Record approved_revision and its manifest reference before starting the transformation. The candidate should identify that exact input, so a later baseline change can be detected instead of silently overwritten by an older operator's output from a stale working session.
Update the approved reference using the team's established safe local workflow only after checks pass. Record candidate revision and validation evidence; do not describe this local pattern as a guarantee that remote retrieval or source state remained unchanged throughout the operation.Identify the current baseline
Record approved_revision and its manifest reference before starting the transformation. The candidate should identify that exact input, so a later baseline change can be detected instead of silently overwritten by an older operator's output from a stale working session.
Write a separate candidate
Use a distinct candidate_path within the permitted artifact area and preserve failure state if writing stops. Do not let readers interpret the candidate as approved merely because it has a familiar title or is located near the released table.
Validate the complete candidate
Parse the entire file, check required schema and reconcile intended membership. A file existing or having nonzero length is insufficient; keep parser and membership failures explicitly attached to the candidate without changing the approved pointer.
Check baseline continuity
Before promotion, compare the current approved revision with the baseline originally read. If another operator changed it, stop and reconcile rather than replacing a newer accepted artifact with a candidate derived from an obsolete assumption about current state.
Promote through existing controls
Update the approved reference using the team's established safe local workflow only after checks pass. Record candidate revision and validation evidence; do not describe this local pattern as a guarantee that remote retrieval or source state remained unchanged throughout the operation.
Keep the boundaries clear.
- Validate a candidate output separately so interrupted writes do not corrupt the accepted table.
- Operational record: Identify the current baseline. 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.