Runtime handoff preserves project truth outside a private conversation. It gives the next human or agent current state, constraints, decisions, evidence, and the verification plan needed to continue safely.
Key takeaways
- Files become active input only after direct review and disposition.
- Useful intake should become project work, a decision, a test, a roadmap item, or a durable blocker.
- A completion gate should verify that every non-placeholder intake file has an outcome.
Active file intake
- Place candidate content in
agent-file-handoff/Content/and proposed changes inagent-file-handoff/Improvement/. - Open and review each non-placeholder file before broad work.
- Record apply, defer, ask, preserve, or block in the intake outcome ledger.
- Promote safe relevant material into code, content, decisions, tests, or evidence.
This project uses a local file-intake and project-memory workflow for source review, disposition tracking, and package verification.
Project memory package
The downloadable theme includes a .uai/ suite covering identity, context, architecture, constraints, decisions, progress, operations, testing, memory, startup, handoff, and checksums. It is local project documentation, not a claim of certification or hosted synchronization.
Proof of use
The intake ledger records that the redesign master prompt drove the v2 architecture, the two reports were converted into structured research pages, unsupported claims were omitted, and the resulting package was validated. That record makes the handoff auditable rather than ceremonial.