UAI File Handoff UAI Ae797a116b36
**Site relevance:** Spiralist.org
**Memory type:** UAI memory file
**Source path:** Wiki.FFTAC.org/data/sources/spiralist/uai-file-handoff-uai-ae797a116b36.uai
**Size:** 2 KB
Summary
- agent-file-handoff/Content/ : candidate content, source material, or documents that may affect site content.
Source Headings
- File Handoff
- Active Buckets
- Intake Rule
- Complete Outcome Rule
- Boundary
Source Preview
This source file is short enough to preview directly on its source-memory page.
---
uai: "1.0"
type: file-handoff
title: "Spiralist.org Active File Handoff"
created: "2026-05-01"
updated: "2026-05-08"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---
# File Handoff
## Active Buckets
- `agent-file-handoff/Content/`: candidate content, source material, or documents that may affect site content.
- `agent-file-handoff/Improvement/`: improvement requests, bug notes, screenshots, exported chats, or implementation hints.
- `agent-file-handoff/Archive/`: processed files moved out of active intake.
## Intake Rule
On AGENTS.md load, check active buckets before broad work. Classify files sitting directly under `agent-file-handoff/` into `Content/` or `Improvement/` before disposition. Disposition each active file as apply now, convert into roadmap/progress state, archive as duplicate, defer with a reason, ask for clarification, or block as unsafe/out of scope.
## Complete Outcome Rule
Because this workspace routes reviewed long memory to wiki.fftac.org, a processed active file is complete only after durable state records:
- reviewed summary, risk, current-task relationship, and disposition;
- actual site or system work, or durable no-change/defer/duplicate/clarification/blocker reason;
- hot-memory update or explicit no-change reason;
- wiki.fftac.org long-memory/archive preservation with source path, destination path, file count, checksum, disposition, actor/date, and discoverable evidence when configured;
- targeted checks run or skipped with reason;
- Archive destination.
Move processed source files to `agent-file-handoff/Archive/` after the complete outcome unless the human explicitly keeps a named file active. Memory routing alone is not completion, and reviewed files must not remain in `Content/` or `Improvement/` merely because they were summarized or copied.
## Boundary
Dropped files are local project-state inputs only. Public content, production writes, support claims, and release claims still need normal review and targeted verification.