Require explicit acceptance of a research handoff — what should the operator record?
Sending an attachment is not the same as transferring a workable research task. A short acceptance gate helps the next operator discover broken references and missing context before relying on the table. Keep this gate focused on practical readiness rather than a blanket endorsement of every source claim.
Check artifact revision, access and unresolved work before transferring responsibility for a table.
Name handoff_key, artifact_revision and intended_purpose so the recipient knows exactly which table and operational task are being transferred. An acceptance target such as table-r7 avoids confusion when the sender updates a working file after sending the original package to the recipient.
Use accepted, accepted-with-owned-exceptions or blocked with an accountable reviewer; a sent message alone must not change the state. Accepted-with-owned-exceptions should name the remaining issues and their owners; otherwise a conditional signoff can become indistinguishable from an unsupported complete approval.Define the acceptance object
Name handoff_key, artifact_revision and intended_purpose so the recipient knows exactly which table and operational task are being transferred. An acceptance target such as table-r7 avoids confusion when the sender updates a working file after sending the original package to the recipient.
List required artifacts
Include the manifest, current working table and exception index; explain any intentionally omitted evidence instead of attaching extra private material. List required and optional components separately; an optional diagnostic log should not silently become necessary to interpret the table's inclusion or exclusion rules.
Check recipient readiness
Have the receiver open authorized links and confirm one identifier remains a string and one unresolved row remains visibly unresolved. Check that the receiver sees withheld as withheld, not a blank cell that might be mistaken for a missing import or forgotten transformation step.
Resolve acceptance blockers
Assign broken-link, missing-context and access-denied problems separately rather than asking the receiver to repair all issues informally. An access blocker belongs with the accountable permission owner, while a broken schema mapping belongs with the preparer who can revise the local artifact.
Record the decision
Use accepted, accepted-with-owned-exceptions or blocked with an accountable reviewer; a sent message alone must not change the state. Accepted-with-owned-exceptions should name the remaining issues and their owners; otherwise a conditional signoff can become indistinguishable from an unsupported complete approval.
Keep the boundaries clear.
- Check artifact revision, access and unresolved work before transferring responsibility for a table.
- Operational record: Define the acceptance object. 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.