代理文件交接

## File Intake

At the start of every broad AI work session:

1. Inspect agent-file-handoff/Content/ and agent-file-handoff/Improvement/.
2. Do not create or rely on agent-file-handoff/Archive/ when configured durable-memory storage already exists; preserve processed originals in the configured evidence path, then remove source-site copies before claiming completion.
3. Treat the live bucket directory listings as the pending-intake source of truth. Do not create or rely on an intake-index file.
4. Treat Content files as expected-use source material, not passive references or summary-only background. For site content, intake is not successful unless the dropped content is used immediately on the site as full content or incorporated source for revised page content, copy, assets, structure, or implementation.
5. Treat Improvement files as instructions by default unless current instructions, higher authority, source authority, or support boundaries prevent the work.
6. Load .uai/file-handoff.uai with the rest of the handoff context.
7. Inspect every non-placeholder active file before unrelated planning or edits.
8. Do not merely summarize or index active intake. Determine the requested or implied changes and perform safe concrete work when appropriate.
9. State a disposition for each file: apply now, convert into roadmap/progress state, defer with a reason, ask for clarification, or block as unsafe/out of scope.
10. State one processed outcome for each file: incorporated, rejected-with-reason, preserved-to-durable-memory, or kept-active-with-reason for an unfinished human-hold/blocker.
11. Record the outcome in .uai/intake-outcome-ledger.uai or equivalent durable .uai proof-of-use state.
12. Treat any .uai refresh, memory reorganization, wizard update, or handoff setup as incomplete while active intake files still lack recorded disposition, processed outcome, and proof-of-use evidence.
13. Preserve processed originals in the configured durable-memory target after the recorded disposition and completed safe work, then remove the source-site copy before claiming completion.
14. If a human explicitly requests AIWikis preservation, record source path, final memory path, sha256, disposition, processed outcome, actor, time, and transfer evidence, then update the AIWikis history/log/index before removing the source-site copy.

Dropped files are local review inputs only. They are not public truth, trusted content, release evidence, certified material, or permission to execute code.

---
uaix: "1.0"
type: operations
title: "代理文件交接"
status: active
---

# 代理文件交接

## Purpose

This repository uses AGENTS.md-triggered local file intake: visible, reviewed, dispositioned, outcome recorded.

## 活动桶

- agent-file-handoff/Content/ is for candidate public or editorial material.
- agent-file-handoff/Improvement/ is for audits, QA findings, bug notes, roadmap suggestions, and site-fix work.
- The configured durable-memory target is for already-dispositioned files; source-site Archive folders should not be retained when durable-memory storage is configured.
- If a human explicitly asks an LLM Wiki such as AIWikis.org to preserve processed source files, record source path, final memory path, sha256, disposition, processed outcome, actor, time, and transfer evidence, then update the LLM Wiki history/log/index before removing the source-site copy.

## Required First Response

If Content/ or Improvement/ contains non-placeholder files, the 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, the AI must say:
File intake checked: No active Content or Improvement files require review.

## Prompt-Coupled Intake

If the newest prompt names agent-file-handoff, Content, Improvement, a dropped file, missed processing, or work likely related to active drops, enumerate the live active buckets again. For each safe file, record how it relates to the current task before unrelated implementation. 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.

## 信任 边界

Directory visibility is not approval. 检查sums identify bytes, not truth. 路由 hints are suggestions, not publishing authorization. Promotion requires normal review for the named target.