Agents - Source Excerpt 01 - AGENTS
Summary
This source excerpt begins near AGENTS and preserves the surrounding evidence from Anti-Christ.org/AGENTS.md.
**Source path:** Anti-Christ.org/AGENTS.md
---
uaix: "1.0"
project: "Anti-Christ.org"
created: "2026-05-10"
updated: "2026-05-10"
status: active
---
# AGENTS
This is the working guide for anyone modifying this repository, including future coding agents.
## Handoff Summary
Anti-Christ.org is a full WordPress site for FFTAC public pages, research surfaces, membership, and signed-in AI console work. Short-term memory lives in this repository's UAIX Project Handoff files; reviewed long-term memory routes to `WP-FFTAC/Wiki.FFTAC.org/`.
## Workspace Coordination
This repo is part of the `WP-FFTAC/` multisite workspace. Before broad work, read `WP-FFTAC/workspace.uai` when the human names any known site/domain, when a request spans multiple sites, or when the current shell directory and requested target differ. Explicit site or domain names decide which handoff bundle to load.
Use the UAIX AI Memory Package Wizard at `https://uaix.org/en-us/tools/ai-memory-package-wizard/` for visible AI Memory setup guidance. Use the LLMWikis setup wizard at `https://llmwikis.org/tools/llm-wiki-setup-wizard/` when planning LLM Wiki structure, pointing reviewed long-memory/cold-memory routing to `WP-FFTAC/Wiki.FFTAC.org/` after source-site review.
## 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 work, inspect `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, classify files sitting directly under `agent-file-handoff/`, ignore `agent-file-handoff/Archive/` unless the human explicitly names an archived file, and review `.uai/intake-index.uai` before unrelated edits.
Dropped files are local review inputs only. Use `.uai/file-handoff.uai` for active bucket, disposition, archive, Wiki.FFTAC.org long-memory, and trust-boundary rules. Reviewed files should leave active intake after the complete outcome is recorded unless the human explicitly keeps a named file active.
## Required First Response
Before broad edits, the next AI should summarize the project and immediate task in 3-5 bullets, name which `.uai` files loaded and whether any were missing or contradictory, confirm constraints that require explicit human approval, name the files/routes/docs it expects to touch, and name the targeted checks it expects to run.
## Read First
1. [README.md](README.md)
2. [readme.human](readme.human)
3. `.uai/context.uai`, `.uai/architecture.uai`, `.uai/decisions.uai`, `.uai/progress.uai`, `.uai/test-plan.uai`, and `.uai/memory.uai` for current hot context.
4. [LLM_WIKI_MEMORY_PLAN.md](LLM_WIKI_MEMORY_PLAN.md) when work needs reviewed long-memory routing through Wiki.FFTAC.org.
5. [AGENT_FILE_HANDOFF_PLAN.md](AGENT_FILE_HANDOFF_PLAN.md) when work touches dropped-file intake.
6. `WP-FFTAC/Wiki.FFTAC.org/wiki/projects/anti-christ.org/docs-archive-2026-05-10.md` when a task explicitly needs the archived former `docs/` material.
Former `docs/` Markdown is no longer site-local hot documentation. It was moved into Wiki.FFTAC.org long memory on 2026-05-10.
## Core Rule
Most custom work belongs in the `Antichrist Engine` presentation theme or FFTAC-owned plugins, not in WordPress core.
Do not edit `wp-admin`, `wp-includes`, bundled WordPress themes, vendor libraries, or third-party license files unless there is a specific WordPress-core or vendor-maintenance reason. The owned hot-memory Markdown files are `README.md`, `AGENTS.md`, `readme.human`, `LLM_WIKI_MEMORY_PLAN.md`, `AGENT_FILE_HANDOFF_PLAN.md`, and `.uai/*.uai`; former `docs/*.md` files are archived in Wiki.FFTAC.org.
Do not treat Wiki.FFTAC.org long memory as current Anti-Christ.org operating truth until a reviewed fact is promoted into this site's hot handoff files, code, release note, or explicit owner decision.
## Where The Real Work Lives
- Theme bootstrap: `wp-content/themes/antichrist-engine/functions.php`
- Foundation plugin bootstrap: `wp-content/plugins/fftac-foundation-core/fftac-foundation-core.php`
- AI Engine plugin bootstrap: `wp-content/plugins/fftac-ai-engine/fftac-ai-engine.php`
- Membership plugin bootstrap: `wp-content/plugins/fftac-membership/fftac-membership.php`
- Public foundation content, page defaults, and datasets: `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`
- Public page provisioning, navigation, API routes, form handlers, private intake exports, and SEO helpers: `wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- User AI console content, personas, protocols, key policy, AJAX handlers, and output sharing: `wp-content/plugins/fftac-ai-engine`
- Front-end membership system: `wp-content/plugins/fftac-membership/inc/membership.php`
- Shared publication helpers: `wp-content/themes/antichrist-engine/inc/template-tags.php`
- Public templates: `wp-content/themes/antichrist-engine/template-*.php`
- Standard WordPress templates: `wp-content/themes/antichrist-engine/search.php`, `single.php`, `archive.php`, `home.php`, `page.php`, `404.php`
- Global styles: `wp-content/themes/antichrist-engine/assets/css/theme.css`
- Theme TypeScript source: `wp-content/themes/antichrist-engine/assets/ts/theme.ts`
- Compiled theme script: `wp-content/themes/antichrist-engine/assets/js/theme.js`
- Large media plugin: `wp-content/plugins/fftac-media-assets`
- Deploy tooling: `scripts/build-deploy-zips.ps1`
- Archived launch runbook: `WP-FFTAC/Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/10-launch-runbook.md`
- Archived user AI architecture: `WP-FFTAC/Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/11-user-ai-architecture.md`
- Active roadmap memory should be promoted into `.uai/progress.uai` or `.uai/decisions.uai` before use.
## Working Rules
- Prefer editing the custom theme for layout, templates, assets, and styling.
- Prefer editing `fftac-foundation-core` for default non-AI copy, datasets, navigation data, public forms, API behavior, SEO, and launch readiness.
- Prefer editing `fftac-ai-engine` for AI console copy, personas, protocols, prompt lanes, key policy, AJAX behavior, and output sharing.
- Prefer editing `fftac-membership` for membership behavior.
- WordPress-admin settings live at `Settings -> FFTAC Foundation`, `Settings -> FFTAC AI Engine`, and `Settings -> FFTAC Membership`; launch readiness and exports live at `Tools -> FFTAC Launch Readiness`.
- Foundation pages are provisioned by the Foundation Core plugin. Changing default public content usually means editing `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`.
- Membership pages are provisioned by the Membership plugin. Changing login, registration, recovery, redirects, or gated access usually means editing `wp-content/plugins/fftac-membership/inc/membership.php` or the membership templates.
- Keep editable source in `E:\antichristorg`.
- Keep `E:\antichristorg-Publish` limited to the WordPress-uploadable theme zip.
- Keep `E:\antichristorg-Plugin-Publish` limited to WordPress-uploadable plugin zips for `fftac-foundation-core`, `fftac-ai-engine`, `fftac-membership`, and `fftac-media-assets`.
- Put full-site server packages in `Releases\`.
- When structure, routing, public data, or responsibilities change, update the relevant `.uai/` hot-memory file and Wiki.FFTAC.org long-memory evidence if the change is durable.
- Do not re-add already implemented theme or plugin work to the roadmap. Future roadmap items should be operational, editorial, external-service, partnership, translation, or data-platform work.
## Fast Routing By Task
- Homepage or public presentation:
`front-page.php`, `header.php`, `footer.php`, `page.php`, `template-*.php`
- Manifesto, philosophy, research, join, journal, downloads, policy, or page default copy:
`wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`
- Philosophy hub layout and Post-Dogmatic Humanism presentation:
`template-philosophy.php`, `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`, `assets/css/theme.css`
- Research atlas, research API, generated exports, focused records, public forms, private intake exports, review notices, topic map, breadcrumbs, SEO, or navigator data:
`wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- Research hub layout:
`template-research.php`, `assets/ts/theme.ts`, `assets/js/theme.js`, `assets/css/theme.css`
- Search and discoverability:
`wp-content/plugins/fftac-foundation-core/inc/foundation.php`, `functions.php`, `header.php`, `search.php`, `searchform.php`, `assets/ts/theme.ts`, `assets/js/theme.js`, `assets/css/theme.css`
- Membership login, registration, recovery, redirects, profile updates, or protected content: