# host-operator — Ramp-down checklist

**Phase:** `ramp_down`
**Exit:** all RD-* complete → set engagement phase to `closed`

| ID | Criterion | Evidence path |
|----|-----------|---------------|
| RD-01 | Open threads triaged | Memory `## Open Threads` resolved or transferred |
| RD-02 | Handoff pack written | `vault/handoff/README.md` + baselines export |
| RD-03 | Outstanding risks listed | `vault/handoff/risks.md` |
| RD-04 | Access revoked / certs not renewed | `access-plan.md` “revoked at …” |
| RD-05 | Schedule disabled | `schedule.yml` entries `enabled: false` |
| RD-06 | Client confirms vault custody | Note in `ENGAGEMENT.yaml` or handoff |
| RD-07 | Supplier workspace scrubbed | No client vault copies outside engagement tree policy |

## Procedure

1. Freeze new duties; finish in-flight session.
2. Triage open threads (human transfer or new engagement).
3. Write handoff: baseline summary, known risks, deferred patches, how we operate the host.
4. Disable schedules; revoke agent access paths.
5. Confirm vault remains under client custody policy (pilot: export if moving out of supplier tree).
6. Scrub any ad-hoc copies outside the engagement vault.
7. Charge ramp-down Kai package; finalise ledger; set phase `closed`.