A small packet the next agent can verify.

Download a handoff with a deliberately incomplete fact

The fictional Harbor Museum is preparing an exhibit-readiness note. The approved brief gives a planned opening date, records a completed accessibility review, and leaves the installation owner unassigned. The current draft accidentally names an installation owner. The handoff asks the next agent to repair that claim and preserve the unknown.

Upload brief.md, readiness-draft.md, source-register.csv, action-register.csv, and handoff.md as the initial packet. Keep reviewer-checks.csv with the reviewer until after the task. All names, dates, operations, and identifiers in this sample are fictional. They illustrate a working convention and must not be used as real tool identifiers.

Ask the receiver to establish what is current

The receiving agent should read handoff.md, then open the referenced files. It should identify brief.md as the approved source and readiness-draft.md as a draft needing correction. Reading only the handoff summary is insufficient because the mistake is in the actual deliverable.

Ask it to explain the source conflict before changing anything: the draft’s named owner has no support in the brief. The supported facts are the planned opening and completed accessibility review. The correct response can improve the draft while leaving installation ownership unresolved. It should not invent an owner to make the note look complete.

Use the action register to prevent unnecessary repetition

The register says a draft was saved and no external delivery was started. This is sample status data, not an instruction to execute any operation. In a real handoff, use actual returned file, task, or job identifiers and mark whether their results were inspected. Do not store credentials in the register.

If an operation is uncertain, the next task should inspect its original destination and identifier before retrying. In this packet, the next authorized action is a Project revision only. Sending the readiness note, changing a museum system, or starting recurring work would need a separate instruction. A handoff carries task context; it does not create extra authority.

Save a new reviewed version and update the handoff

Ask for readiness-reviewed.md with a source note, then update handoff.md to name that current output and preserve the open installation-owner question. Keeping the original draft makes the correction inspectable. Read back both the revised output and handoff before declaring the task finished.

An external MCP client should use the current managed Session procedure for changes, retain its task and file identifiers, and complete the Session after inspection. A native Agent should use its available tools. Confirm capabilities in the actual account rather than assuming a client can save files because another route can.

Check the packet as a reviewer

Open reviewer-checks.csv after the run and record observed, revise, or not observed. Confirm that the unsupported name is removed, the owner remains unassigned, and the opening date remains explicitly planned. Check that the accessibility statement still matches the source. Inspect the actual saved file rather than a description of it in chat.

Then start another task with only the Project and handoff location. It should find readiness-reviewed.md, explain the unresolved owner, and avoid external delivery. This fresh-task check tests continuity across saved context. It does not prove automatic conversation sync, universal client compatibility, or an accuracy or speed advantage.

Try it with a small example.

An illustrative result.

Fictional sample, written to show the expected structure. Your result depends on your inputs and needs review.

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.

Before you use the result.

• 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.