Skip to content
wiki.fftac.org

FFTAC Readme

**Site relevance:** FFTAC.org

**Memory type:** reviewed source memory

**Source path:** FFTAC/readme.human

**Size:** 2.4 KB

Summary

FFTAC.org Human Briefing

Source Headings

  • FFTAC.org Human Briefing
  • What You Need To Know
  • Things The AI Will Defend
  • Things Humans Should Make Explicit

Source Preview

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

# FFTAC.org Human Briefing

Updated: 2026-05-11

This file is for humans working with AI on this repository. It explains what the AI sees, protects, and needs clarified. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, laws, policies, or the current human request.

## What You Need To Know

- FFTAC.org is a WordPress Studio site for the Foundation For The Anti-Christ "Who We Are" public information surface.
- The AI reads `AGENTS.md` first, then this file, then the `.uai` files listed under Loaded Context.
- Short-term memory lives in `AGENTS.md`, `readme.human`, `.uai/`, and `agent-file-handoff/`.
- Long-term reviewed memory routes to `WP-FFTAC/Wiki.FFTAC.org/`.
- Short-term working memory follows `https://uaix.org/en-us/tools/ai-memory-package-wizard/`; long-term reviewed memory follows `https://llmwikis.org/tools/llm-wiki-setup-wizard/` pointed at Wiki.FFTAC.org / `wiki.fftac.org`.
- Processed handoff files should not remain in active `Content/` or `Improvement/`; they should be archived after disposition and preserved through Wiki.FFTAC.org when durable.
- Production packaging runs a handoff audit and should fail if active intake is unresolved.
- The working tree may already contain unrelated user or runtime changes. The AI should inspect before editing and should not revert work it did not create unless explicitly asked.

## Things The AI Will Defend

- Secrets, credentials, private keys, tokens, customer data, and private material.
- WordPress core, vendor code, bundled third-party assets, and generated runtime artifacts.
- Evidence boundaries for public claims, support/security language, and deployment readiness.
- Targeted verification before claiming that code, packaging, or release behavior is ready.

## Things Humans Should Make Explicit

- Whether the task may touch production, public content, legal/security/support language, or irreversible data.
- Whether package ZIPs should be rebuilt or uploaded.
- Whether durable hot memory and Wiki.FFTAC.org long memory should be updated after the change.
- Which checks are required before the work is considered done.
- Whether dropped files in `agent-file-handoff/Content/` or `agent-file-handoff/Improvement/` should be applied, deferred, or ignored.
- Whether any current-organization or extremist-adjacent links from research archives should be public, internal-only, summarized without links, or blocked.
Website health report