Package a multi-file research export with a manifest — what should the operator record?
An export bundle may contain a table, coverage notes and a transformation log. Without an index, recipients can mistake unrelated revisions for one coherent release. A manifest links the files that belong together, while keeping sensitive row details out of broadly visible filenames and package inventories.
Connect related files through a minimal manifest without leaking evidence into archive names or indexes.
Assign bundle_revision and list each permitted file's role, relative path and source table revision without embedding account names in archive labels. A role list such as table, coverage and transform-log makes missing components visible without exposing the underlying source subjects in archive directory names.
Provide the receiver with the manifest revision and unresolved omissions, avoiding a complete label if any required artifact failed reconciliation. If one optional artifact is omitted, say so explicitly; if a required artifact fails, keep the entire release blocked rather than relying on archive extraction success.Define the bundle boundary
Assign bundle_revision and list each permitted file's role, relative path and source table revision without embedding account names in archive labels. A role list such as table, coverage and transform-log makes missing components visible without exposing the underlying source subjects in archive directory names.
Check internal references
Ensure coverage notes and transformation logs point to the table actually included, not a newer local file omitted from the package. Include referenced_revision for each dependency; a correct filename with outdated contents should still fail the package consistency check before the bundle is released.
Validate files independently
Parse every listed file and compare its membership or metadata to its declared role; an archive opening successfully is not content validation. A coverage note should be valid text and match the declared query and window, while the table needs schema and membership checks appropriate to its representation.
Review bundle permissions
Confirm every included file is allowed for the intended recipients, removing unnecessary diagnostic material through the approved packaging process. Do not include a raw response solely because it might help troubleshooting if the intended recipients only need a minimized table and an operational exception index.
Publish the checked inventory
Provide the receiver with the manifest revision and unresolved omissions, avoiding a complete label if any required artifact failed reconciliation. If one optional artifact is omitted, say so explicitly; if a required artifact fails, keep the entire release blocked rather than relying on archive extraction success.
Keep the boundaries clear.
- Connect related files through a minimal manifest without leaking evidence into archive names or indexes.
- Operational record: Define the bundle boundary. 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.