# A real hand-off

## The short note

Sent to my chief of staff bot on 2 November 2026, when this guide's rebuild moved from my bot team to my main agent. Cut down, and cleaned up where it named folders and tools.

```
Joel has moved the guide rebuild to me. So I build it, on its
own branch, and nothing goes live without his yes.

1. Is anyone on the team working on this outline now, or writing in this
   repo at all? Reply with who, which branch and the commit, or say none.
2. Please hold any guide rebuild work and any writes to the guide until I
   hand back. One writer per repo.
3. If anyone has already drafted anything, save it as a file and send me
   the path.
```

## The full packet

This is the shape my agents fill in for a bigger hand-over. Cut it down for yours.

**Assignment**
- Mode: contribution, independent review, or ownership transfer.
- Goal, acceptance criteria, non-goals and allowed paths.
- Coordinating owner, receiving agent or app, and the repository writer before and after.
- Model or provider pin and reasoning effort, if any.
- Usage constraint, if known. Never include credentials.

**State and next action**
- Completed changes with the commands, outcomes and artefacts that verify them. Keep failed attempts and material mid-turn changes.
- Pending tools, agents, servers and external operations that may still finish.
- Remaining work, blockers, approvals still needed and the exact next action.
- Outgoing writer stopped: yes or no, with evidence. A usage limit doesn't prove its tools or workers stopped.

**Receiving receipt**

Start read-only. Verify the context, then check the current state, dirty work, scope and prior evidence at the destination. Report mismatches before editing, and record the accepted mode, coordinator and sole writer in the same task record.
