# TRANSFER AND RECOVERY CHECKLIST

## Transfer

- [ ] The new operator can state the system's purpose.
- [ ] The new operator knows which source owns each current fact.
- [ ] The new operator can distinguish memory, current state, plan, and proof.
- [ ] The new operator can explain what AI may do automatically.
- [ ] The new operator can find every human gate.
- [ ] The new operator can run the normal workflow.
- [ ] The new operator can inspect the evidence.
- [ ] The new operator can stop the system.
- [ ] The new operator can recover without rebuilding it from scratch.
- [ ] The original builder remained silent during the final demonstration.

## Recovery

- [ ] Stop new actions.
- [ ] Preserve the failure evidence.
- [ ] Identify the last known good state.
- [ ] Check for duplicates or partial external effects.
- [ ] Correct the governing source, not only the latest output.
- [ ] Use the manual fallback if the work still matters.
- [ ] Rerun the failed case with synthetic or safe input.
- [ ] Record what changed.
- [ ] Notify the responsible human if an external consequence occurred.
- [ ] Resume only after the success and stop controls are proven.

## Seven-day review

- What did the system finish?
- What did it prevent or catch?
- What context was still repeated?
- What did it get wrong?
- Which approval was unnecessary?
- Which approval was missing?
- What should be removed?
- Would another operator keep using it?
