---
uaix: "1.0"
type: file-handoff
status: active
title: "Agent File Handoff"
updated_utc: "2026-06-29T00:00:00Z"
setup_url: "https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-file-handoff"
combined_setup_url: "https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-file-handoff-llm-wiki"
---

# Agent File Handoff

## Purpose

This repository uses local file intake: visible, reviewed, dispositioned, outcome recorded, and preserved to durable memory when configured.

## Active buckets

- `agent-file-handoff/Content/` is for candidate public or editorial material, reports, drafts, screenshots, source summaries, and content candidates.
- `agent-file-handoff/Improvement/` is for audits, QA findings, bug notes, roadmap suggestions, strategy, and site-fix work.
- The configured durable-memory target is `/docs`; source-site archive folders should not be retained when durable-memory storage is configured unless a human explicitly asks for that.

## Required first response

If Content or Improvement contains non-placeholder files, the receiving AI must summarize each file, name the risk, recommend a disposition, choose one processed outcome, name the target surface, and name checks needed before unrelated broad work.

If no active files are pending, state:

`File intake checked: No active Content or Improvement files require review.`

## Intake completion gate

A handoff setup, memory refresh, or continuation is incomplete while active `Content`, active `Improvement`, or a misplaced root intake file lacks:

1. bucket scan evidence;
2. recorded disposition;
3. one processed outcome;
4. proof of use or blocker state;
5. durable preservation evidence when `/docs` is the configured target;
6. source-site removal state or explicit keep-active reason.

Allowed processed outcomes:

- `incorporated`
- `rejected-with-reason`
- `preserved-to-durable-memory`
- `kept-active-with-reason`

## Durable memory link rule

When a file becomes long-term memory:

- place the full body under `/docs/reports` or `/docs/memory`;
- record the destination checksum;
- add a compact pointer to `.uai/long-term-memory.uai`;
- add a report pointer to `.uai/report-pointer-ledger.uai` when the destination is a report;
- append outcome evidence to `.uai/intake-outcome-ledger.uai` and `/docs/memory/promotion-and-intake-ledger.md`.

## Prompt-coupled intake

If the newest prompt names `agent-file-handoff`, `Content`, `Improvement`, a dropped file, missed processing, UAI memory, long-term memory, or work likely related to active drops, enumerate the live active buckets again. Related files must shape actual project work, not only memory routing.

## Blocked extensions

Block automatic execution for `.bat`, `.cmd`, `.exe`, `.msi`, `.phar`, `.php`, `.php3`, `.php4`, `.php5`, `.phtml`, `.ps1`, and `.sh` files supplied through intake.

## Trust boundary

Directory visibility is not approval. Checksums identify bytes, not truth. Route hints are suggestions, not publishing authorization. Promotion requires normal review for the named target.