Anti Christ Readme
**Site relevance:** Anti-Christ.net
**Memory type:** reviewed source memory
**Source path:** Anti-Christ.net/readme.human
**Size:** 1.9 KB
Summary
Anti-Christ.net Human Briefing
Source Headings
- Anti-Christ.net 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.
# Anti-Christ.net Human Briefing
Updated: 2026-05-10
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
- Anti-Christ.net is a WordPress Studio site with the custom `anti-christ-thin-veil` theme.
- 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`.
- The site currently has limited local project documentation, so the theme README and `.uai` files carry most of the working context.
## Things The AI Will Defend
- Secrets, credentials, private keys, tokens, customer data, and private material.
- WordPress core, third-party plugin code, bundled assets, and generated runtime artifacts.
- The boundary between current theme behavior and reviewed long-memory evidence.
- Targeted verification before claiming that code, packaging, or release behavior is ready.
## Things Humans Should Make Explicit
- Whether the task may touch production, public copy, security/support language, plugins, 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.