Create a manifest for a returned research snapshot — what should the operator record?
A folder of result files is difficult to reconstruct when query wording, return time and coverage notes live elsewhere. Build one manifest alongside the returned evidence so the next operator can identify the exact input before transforming or comparing anything.
Attach query, receipt and coverage metadata to an evidence snapshot without treating a local copy as permanent source access.
Use a local snapshot_key such as review-nov-a and record received_at, workspace_alias and the original question without embedding credentials. For example, distinguish review-nov-a from review-nov-b even if both files came from the same question on the same day.
Have the receiving operator confirm the manifest matches the evidence they can currently access before they begin a downstream table. The acceptance record should identify the manifest revision checked, so replacing the table later cannot inherit a signoff for different input bytes.Name the evidence batch
Use a local snapshot_key such as review-nov-a and record received_at, workspace_alias and the original question without embedding credentials. For example, distinguish review-nov-a from review-nov-b even if both files came from the same question on the same day.
Separate time meanings
Store received_at beside any returned publication timestamp; the time you saved a file must not replace the time evidence appeared. An internal manifest might show received_at with an offset and source_published_at as date-only; that difference must survive any later spreadsheet import.
Link the working copy
Add input_path, permitted_until and transform_revision to the manifest; use relative internal paths rather than publicly accessible download links. Keep transform_revision attached even when the operation only removes columns, because a smaller table can still have the same underlying evidence membership.
Check the manifest join
Open a working row and follow snapshot_key back to the response. Reject orphaned rows instead of assigning the newest available snapshot. A manifest pointing to an unrelated question is a provenance failure even if its row count happens to match the working table exactly.
Approve the handoff
Have the receiving operator confirm the manifest matches the evidence they can currently access before they begin a downstream table. The acceptance record should identify the manifest revision checked, so replacing the table later cannot inherit a signoff for different input bytes.
Keep the boundaries clear.
- Attach query, receipt and coverage metadata to an evidence snapshot without treating a local copy as permanent source access.
- Operational record: Name the evidence batch. 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.