Antichrist Readme
**Site relevance:** Antichrist.net
**Memory type:** reviewed source memory
**Source path:** Antichrist.net/readme.human
**Size:** 2.2 KB
Summary
Antichrist.net Human Briefing
Source Headings
- Antichrist.net Human Briefing
- What You Need To Know
- Current Known Fix
- 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.
# Antichrist.net Human Briefing
Updated: 2026-05-12
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
- Antichrist.net is the relaunching WordPress Studio site at `WP-FFTAC/Antichrist`.
- 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/`.
- The setup tools stored for this project are:
- `https://uaix.org/en-us/tools/ai-memory-package-wizard/`
- `https://llmwikis.org/tools/llm-wiki-setup-wizard/`
## Current Known Fix
The local Studio admin warning from Participants Database was caused by PHP sessions pointing at missing `/home/web_user` storage. The MU-plugin at `wp-content/mu-plugins/antichrist-studio-session-path.php` sets a writable session path under `wp-content/cache/php-sessions`.
## Things The AI Will Defend
- Secrets, credentials, private keys, tokens, customer data, and private material.
- WordPress core, third-party plugin code, bundled assets, SQLite integration, and generated runtime artifacts.
- The boundary between current site behavior and reviewed long-memory evidence.
- Targeted verification before claiming that code, packaging, or release behavior is ready.
- The public editorial stance: do not name anyone as the Antichrist; study traditions, systems, symbols, and accusation history instead.
## 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.