“For Atlas, prepare a launch checklist for 24 September. Maya can review.”
LAB / HANDOFF 001
What can one note change?
Connect the missing context, make a decision, and inspect the handoff. A synthetic example with a simulated AI step; no message is sent and no date is confirmed.
Simulated AI step · nothing sent.
ATLAS / HANDOFF 00101 / A REQUEST ARRIVES
A few words.
A lot left unsaid.
There is enough here to begin. There is not enough to treat every detail as settled.
“Maya can review” does not tell us who owns the work or who can approve the release.
Bring in the missing context02 / CONTEXT CHANGES THE ANSWER
One note changes
the handoff.
Connect the team’s note. Watch what becomes known—and what still needs a person to decide.
“Noah owns Atlas. Maya approves release work. The launch date is still provisional.”
Owner and release approver remain unknown. 24 September is a request, not a confirmed date.
Inspect source ADisconnecting the note removes its facts from the handoff. The example does not keep an answer it can no longer support.
Decide what happens next03 / YOU CHOOSE WHAT HAPPENS NEXT
A useful system
leaves room for judgment.
The request is the same. Your choice changes the next action, the status and the handoff.
Decision needed
Choose whether to clarify the missing information or prepare a reviewable draft. No action has been taken.
This changes the sample only. No message goes to Maya or Noah. No date is confirmed and nothing is scheduled.
Inspect your handoff04 / THE CONTEXT STAYS INTACT
Not just an answer.
Something a team can act on.
Your handoff keeps the request, connected evidence, unresolved details and chosen next action together. Inspect it, change the decision or copy the actual sample text.
Your next work product
Choose a next action to assemble a clarification message or a draft checklist. The evidence remains available to inspect and copy.Keep the sample or start a project conversation. Including this example in an inquiry is optional.