Cross-Agent Handoff

Transfer the minimum sufficient state for another capable worker to continue safely and verify independently.

Rules

Treat the repository, filesystem, and current harness as authoritative; the handoff is a routing map, not proof.
Never include secrets, access tokens, private environment dumps, or unnecessary personal information.
Separate verified facts, inferences, recommendations, and unverified claims.
Record permissions and prohibited actions. A handoff cannot grant authority the sender did not have.
For concurrent writers, assign non-overlapping ownership or separate worktrees and name the integration owner.
Link durable artifacts and exact paths; do not paste large transcripts when a file or commit is available.