Departure evidence path — textual equivalent FICTIONAL REVIEW ONLY. Actual app execution: Not tested. Operational lane: 1. Complete declared scope: three staff; eight composite task identities across desk-east and desk-west; before/after exports include every status and assignee. 2. A proposed recipient is a nomination, not an observed handoff. Match task ID, partition, before owner and revision. 3. Confirm separate prerequisites: active operational profile, explicit partition membership and task-type receive grant; task/revision-specific acceptance; explicit reviewer authority. A Coordinator label proves none of these. 4. Match a separate handoff receipt and complete after-record to the same identity, revisions and recipient. Keep original creator/closer/time/history; append only supplied handoff events. 5. Count within complete scope. C01: two supported transfers, T03 still assigned to STAFF-A, operational review BLOCKED. C15 alternative: three supported transfers, zero remaining for STAFF-A, eligible within declared fictional scope. Both retain five open tasks and three closed tasks; no action occurs. Independent security lane, deliberately NOT downstream of operational completion: SECURITY-A-1 records access already revoked at 08:55, before the operational review. Necessary revocation must not wait for a completed handoff. Neither case changes, restores or delays access. Operational STAFF-A profile remains active in both supplied cases. Boundary rail: Missing/partial/stale/unknown/contradictory evidence blocks the affected conclusion. Preserve positive observed matches and raw after-owners separately from proof of authorized handoff. C14 contains eight raw rows but only seven composite keys, not eight reconciled tasks.