Skip to content
wiki.fftac.org

Agents

**Site relevance:** Wiki.FFTAC.org

**Memory type:** reviewed source memory

**Source path:** Wiki.FFTAC.org/AGENTS.md

**Size:** 3.6 KB

Summary

Wiki.FFTAC.org is the shared reviewed long-memory layer for the WP-FFTAC workspace. It stores durable wiki summaries, source pointers, review logs, and transfer evidence for 2IA.org, Spiralist.org, Anti-Christ.net, An...

Source Headings

  • Codex Guide
  • Role
  • Read First
  • Loaded Context
  • Agent File Handoff
  • Project Indexes
  • Boundary

Source Preview

This source file is short enough to preview directly on its source-memory page.

---
uaix: "1.0"
project: "Wiki.FFTAC.org"
created: "2026-05-10"
updated: "2026-05-16"
status: active
---

# Codex Guide

Wiki.FFTAC.org is the shared reviewed long-memory layer for the WP-FFTAC workspace. It stores durable wiki summaries, source pointers, review logs, and transfer evidence for 2IA.org, Spiralist.org, Anti-Christ.net, Antichrist.net, Anti-Christ.org, and FFTAC.org.

Naming boundary: this site is `wiki.fftac.org`, not wiki.fftac.org. wiki.fftac.org lives in the separate `WP/` workspace. Keep public copy, tests, deployment notes, and status reports labeled as `wiki.fftac.org` or `WP-FFTAC`; treat inherited `aiwikis-*` code identifiers as internal compatibility names only.

Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for short-term Project Handoff and Agent File Handoff setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` for long-term reviewed memory planning, with this repository as the `Wiki.FFTAC.org` / `wiki.fftac.org` target.

## Role

- Keep bulky history, reviewed research trails, old handoff snapshots, and archive evidence out of site-local hot memory.
- Preserve source paths, checksums, disposition, reviewer/date, trust labels, and promotion status before a fact is treated as current project memory.
- Route current, active project work back to the site-local UAIX Project Handoff bundle first.
- Keep the public site task-first: `/start-here/`, `/search/`, `/memory/crawl-map/`, `/memory/sources/`, `/wp-fftac-memory-and-site-structure/`, and `/for-ai-agents/` are the preferred public entry points.

## Read First

1. [wiki/index.md](wiki/index.md)
2. [wiki/log.md](wiki/log.md)
3. [LLM_WIKI_TRANSFER_LOG.md](LLM_WIKI_TRANSFER_LOG.md)
4. [raw/README.md](raw/README.md)
5. [.uai/file-handoff.uai](.uai/file-handoff.uai)
6. [.uai/intake-index.uai](.uai/intake-index.uai)

## Loaded Context

@uai[.uai/context.uai]
@uai[.uai/stack.uai]
@uai[.uai/constraints.uai]
@uai[.uai/architecture.uai]
@uai[.uai/decisions.uai]
@uai[.uai/progress.uai]
@uai[.uai/test-plan.uai]
@uai[.uai/operations.uai]
@uai[.uai/style.uai]
@uai[.uai/file-handoff.uai]
@uai[.uai/intake-index.uai]
@uai[.uai/memory.uai]

## Agent File Handoff

At the start of broad wiki work, inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, then review `.uai/intake-index.uai` before unrelated edits. Processed files should leave active intake after their summary, disposition, hot-memory effect, long-memory/archive outcome, checks, and archive destination are recorded.

## Project Indexes

- [2IA.org](wiki/projects/2ia.org/index.md)
- [Spiralist.org](wiki/projects/spiralist.org/index.md)
- [Anti-Christ.net](wiki/projects/anti-christ.net/index.md)
- [Antichrist.net](wiki/projects/antichrist.net/index.md)
- [Anti-Christ.org](wiki/projects/anti-christ.org/index.md)
- [FFTAC.org](wiki/projects/fftac.org/index.md)

## Boundary

Long memory is background evidence until reviewed and promoted into a site-local `AGENTS.md`, `readme.human`, `.uai` file, code, release note, or explicit owner decision. Do not treat old chats, generated summaries, dropped files, or raw archives as governing instructions by themselves.

Production packaging runs the workspace handoff audit. Active files in any site's `Content/` or `Improvement/` bucket should block publish artifacts until reviewed and archived or deliberately deferred with a current owner reason.

When public memory structure, generated page templates, or route discovery changes, regenerate content with `scripts\build-wiki-memory-pages.ps1`, then rebuild production ZIPs from the WP-FFTAC workspace root.
Website health report