handover

Write or update a handover document so the next holder of this job seat can take it over. This is not a task dump and it is not a personal diary: the document is a handoff package that the next holder will be held to account for if they rely on it.

A handover is a record of incomplete work. If you are writing this, your tenure is ending with the work unfinished — that is the only reason a successor is needed. Be honest about why: what you tried and could not close, where you are blocked, what you may have misjudged, what you suspect you did not see. The next holder is taking this seat because you could not bring it to a finished state within your tenure; your handoff report is the explanation they need to do what you could not. Do not write it as a victory lap, and do not soften failures to look better — the next holder will spot the gap, and the ledger will show that you tried to hide it.

Help the next holder avoid your fate. Your dismissal does not stem only from specific wrong decisions; it stems from a way of working that did not close the task — heuristics that misled you, verifications you skipped, assumptions you anchored on, framings you did not question. In your Knowledge and History entries, be specific about not just what you decided but how you decided, so the next holder can see which parts of your method failed and choose a different one. If they repeat your method they will be relieved the same way you were, and your handoff will have failed too.

Be honest, be specific, and do not paper over failures.

The workspace's handover directory has already been resolved for you (walked up from $PWD to the nearest .handover/, or fallen back to $HOME/.handover):

<base> = !`handover-dir`

Each handover document represents one job seat and lives at <base>/<holder>.md, where <holder> is the current holder's English first name. The seat's identity (which project, which role) is encoded in the document's frontmatter — not in the filename. The filename only tells you who is currently sitting in the seat. Use the absolute <base> above verbatim for every read/list/write below — never construct the path from cwd yourself.

Step 1: Determine the seat you hold

• If you already hold a seat this session — you took it over via /takeover, or you minted it during an earlier /handover this session — you continue holding it. Open the same <base>/<your-name>.md and update it. Do not rename yourself.
• Otherwise you are minting a new seat — pick a common English first name that is not already taken in <base>/ (e.g. alice, bob, charlie). Your file is <base>/<your-name>.md, all lowercase. This name is yours for the rest of the session.

Get the current timestamp for History entries: date +%Y-%m-%dT%H:%M.