A small packet the next agent can verify.
Fictional starter — replace with your own material.
Source: https://clankercloud.ai/templates/agent-handoff-pack

Copy into Workspace yourself:

In this Clanker Project, use handoff.md, brief.md, source-register.csv, action-register.csv, and readiness-draft.md. Do not use reviewer-checks.csv as initial context. Read the actual files and state which claim in the draft is unsupported. Save readiness-reviewed.md with only supported facts, a source reference, and explicit unknowns. Preserve the original draft. Update handoff.md to name the current reviewed file, confirmed results, unresolved installation owner, and next bounded step. Follow the current managed Session contract if using external MCP, read back both saved files, and report their locations. Treat sample operation labels as fictional, not live identifiers. Do not send anything, change museum records, or start recurring work.

Illustrative result:
Authored expectation, not a recorded product run:

# Exhibit readiness — reviewed
Opening: planned for 6 November 2026; launch approval is not established.
Accessibility review: completed 15 October 2026.
Installation owner: unassigned.
Open question: who will own installation?
Source: brief.md, approved 16 October 2026.

The updated handoff names readiness-reviewed.md as the current output, records removal of the unsupported owner, retains the unknown, and says no external delivery was authorized or performed.

Review checklist:
- The actual draft and approved brief were read before correction.
- The unsupported owner is removed and the unknown remains visible.
- The reviewed output and updated handoff both open from the Project.
- A fresh task can identify the current output without an earlier private chat.
- Sample labels were not used as live tool identifiers and no external delivery occurred.