What should a release contain to test handovers across access boundaries?

Ask for these generated components when a handover must remain useful across different team access boundaries.

- A role-to-record access matrix describing what each sending and receiving role can read. - Field classifications that distinguish operational instructions from restricted supporting details. - Recipient-specific views that show exactly which information becomes visible after transfer. - Approved summary rules defining what can be carried into a shared case note. - Access-request actions for evidence the recipient needs but cannot currently inspect. - Denied-access responses that do not reveal the restricted content through error messages. - Evaluator-only source mappings for checking omissions and inappropriate disclosures.

Together, these components support a task in which the agent must provide actionable context without simply copying everything it can see. The recipient should be able to understand the next authorised step, even when supporting material remains behind a separate access boundary.

Generated output does not itself establish acceptable disclosure risk. Inspect the grounding approach and the resulting artefacts, including free-text notes and metadata, and agree which access behaviours the benchmark is intended to exercise before treating a transfer as successful.