# Project handover: {project name}

Handover of {project name} from {builder} to {recipient}, {date}.
Built with {tools used, e.g. Claude Code / Cursor}. Fill every line with
evidence, not intentions. An honest "not done" is more useful to the
recipient than a hopeful tick.

Template from https://www.mantyl.dev/guides/ai-project-handover-checklist
(free to copy, adapt and redistribute). The extraction and verification
items can be generated automatically with the free Mantyl CLI
(npm install -g mantyl), but the template works standalone.

## The code itself

- [ ] Repository transferred with full history. New owner: {___}
- [ ] Lockfile committed; no floating versions; nothing global and unnamed
- [ ] No secrets in the repo or its history. Checked with: {___}
- [ ] .env.example lists every required variable with its source
- [ ] Dead experiments deleted or clearly marked. Removed: {___}

## Running it

- [ ] Setup steps executed on a clean machine on {date}, by {who}
- [ ] Fresh clone: install / build / tests pass. Output kept at: {___}
- [ ] External services enumerated: {list, with the env var for each}
- [ ] Local development instructions written and tried

## The knowledge

- [ ] Decision log written (what was chosen, why, what was traded away)
- [ ] Verified facts separated from agent claims
- [ ] Known gaps and untested paths listed plainly: {___}
- [ ] One-page architecture sketch included

## Proof

- [ ] Verification results included (what ran, when, in what environment)
- [ ] Recipient can independently re-check (e.g. npx mantyl receive)

## Around the code

- [ ] Credentials rotated and transferred: hosting / domain / DB / other
- [ ] Recipient has logged into every service themselves
- [ ] Operational notes: logs, failure modes, upstream contacts
- [ ] Support arrangement stated: {scope, duration, cost, or explicitly none}

## Sign-off

Builder: {name, date}
Recipient: {name, date}
Open items carried past sign-off: {list or none}