# File Handoff and Project Handoff Plan

Updated: 2026-06-04

## File Handoff

The package includes an `agent-file-handoff/` intake deck. It exists so a receiving AI or human reviewer can separate active source files from requested improvements and processed archive records.

- `agent-file-handoff/Content/`: source content expected to be reviewed and used.
- `agent-file-handoff/Improvement/`: requested improvements, issues, or enhancement notes.
- `agent-file-handoff/Archive/`: processed source files or closed requests.
- `.uai/intake-outcome-ledger.uai`: durable proof that intake files were accepted, rejected, summarized, or moved.

## Project Handoff

The `.uai/project-handoff.uai` record directs the next session to inspect this WordPress theme, confirm target site root, review the public copy, inspect the downloadable resume assets, and use `/docs/` as durable long-memory research before editing.

## Acceptance rule

A handoff is not complete unless the receiving agent can answer these checks:

1. Which `.uai` file gives the active short-term memory?
2. Which `/docs/` Markdown files support durable research claims?
3. Which theme files changed the public site copy?
4. Which downloadable resume files are currently linked?
5. Which files were processed from the handoff intake deck?