Write a work handover document

Write a handover document.

Order by when the successor needs it:
1. **This week** — anything with a deadline inside two weeks, what state it is in, what the next action is.
2. **Recurring** — what happens weekly and monthly, with the trigger and the deadline. Things nobody notices until they are missed.
3. **Who to contact for what.** Names, what they handle, and *how they prefer to be reached* — the part that never gets written down.
4. **Access** — systems, accounts, shared files, physical things. What needs transferring and who grants it.
5. **Undocumented knowledge.** The section that matters. Prompt me with questions:
   - What breaks regularly that you just know how to fix?
   - What looks wrong but is intentional?
   - Which request should never be agreed to without checking?
   - What did you learn the hard way?
   - What would you warn a friend about on their first day?
6. **In flight with a history** — work where the current state only makes sense if you know what was already tried.

Then: the three things that will go wrong first if this document is all they get.

Rules:
- *Do not write generic handover advice.* Work only from what I gave you, and ask for what is missing.
- Name people as roles where naming individuals would be inappropriate, but keep names where the successor needs them.
- Flag anything needing a conversation rather than a document.