Skip to content
wiki.fftac.org

File Handoff

**Site relevance:** Anti-Christ.org

**Memory type:** UAI memory file

**Source path:** Anti-Christ.org/.uai/file-handoff.uai

**Size:** 1.7 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: "Anti-Christ.org Active File Handoff"
created: "2026-05-10"
updated: "2026-05-10"
status: active
source: "https://uaix.org/en-us/specification/agent-file-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, audits, 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.

## 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.
Website health report