05 Editing Guide - Source Excerpt 02 - Provisioning Note
Summary
This source excerpt begins near Provisioning Note and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/05-editing-guide.md.
**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/05-editing-guide.md
- noindex, nofollow, `robots.txt`, `X-Robots-Tag`, canonical, and sitemap discovery behavior
- localized launch visibility state for front-end scripts
- client-side analytics event names and payloads
The default launch visibility is `public`. Use `Settings -> FFTAC Foundation`, the `ANTICHRIST_ENGINE_LAUNCH_VISIBILITY` constant, matching environment variable, or `antichrist_engine_launch_visibility` option to set `preview` or `private` only for staging, review, or intentionally hidden environments. For production indexing, keep launch visibility public and make sure WordPress Search Engine Visibility is also enabled.
Use `Tools -> FFTAC Launch Readiness` in WordPress admin to review the Foundation Core prelaunch checks, go-live operations checklist, launch handoff TXT export, and private intake CSV exports. Do not treat that page as a substitute for host-level TLS, WAF, backups, monitoring, analytics, email, or support setup.
Use [10-launch-runbook.md](10-launch-runbook.md) for the final go-live sequence and stop conditions.
Use [11-user-ai-architecture.md](11-user-ai-architecture.md) before changing the AI console, key policy, session tools, local snapshots, hidden personas/protocols, share behavior, or AJAX endpoints.
## Provisioning Note
Some pages are created and filled by FFTAC plugin code.
That means:
- new installs pick up defaults automatically
- existing installs may already have created pages
- version bumps in `wp-content/plugins/fftac-foundation-core/inc/foundation.php` and `wp-content/plugins/fftac-membership/inc/membership.php` can refresh provisioned records
- direct edits made in WordPress admin are treated as manual divergence and should not be blindly overwritten
## Good Editing Pattern
1. Find the owning file before editing.
2. Change the source of truth, not only the nearest rendered template.
3. Keep default non-AI copy and reusable datasets in `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`.
4. Keep routing, forms, API behavior, and metadata in `wp-content/plugins/fftac-foundation-core/inc/foundation.php`.
5. Keep user AI server behavior and AI-specific prompt/content data in `wp-content/plugins/fftac-ai-engine`.
6. Keep authentication and gated access in `wp-content/plugins/fftac-membership/inc/membership.php`.
7. Keep layout in templates.
8. Keep styling in `assets/css/theme.css`.
9. Keep client-side behavior in `assets/ts/theme.ts` and compile `assets/js/theme.js`.
10. Update docs when structure, routes, exports, public data, or responsibilities change.
## Brand Naming
Use:
- `FFTAC`
- `The Foundation`
- `Foundation For The Anti-Christ`
Avoid misspellings and alternate casing such as `FFAC`, `Foundation For the Anti-Christ`, or `The Foundation For The Anti-Christ` in public-facing copy and record IDs.
## Roadmap Rule
Do not put completed theme or FFTAC plugin work back into the future roadmap.
Use [07-infrastructure-roadmap.md](07-infrastructure-roadmap.md) only for work that still needs operational setup, external services, editorial process, partnerships, translations, analytics, security, hosting, or a data platform beyond plugin-backed arrays.
## Publish And Release
- Source edits belong in `E:\antichristorg`.
- Markdown files are internal instructions and should not be treated as public site content.
- `E:\antichristorg-Publish` should contain only the WordPress-uploadable theme zip.
- `E:\antichristorg-Plugin-Publish` should contain WordPress-uploadable plugin zips for Foundation Core, AI Engine, Membership, and Media Assets.
- Full-site packages belong in `Releases\`.
- Build deploy packages with `scripts/build-deploy-zips.ps1`.
- See [deploy.md](deploy.md) for which zip belongs where.
## Verification
After PHP edits:
' ' ' powershell
php -l wp-content/themes/antichrist-engine/functions.php
php -l wp-content/plugins/fftac-foundation-core/inc/foundation.php
php -l wp-content/plugins/fftac-ai-engine/inc/ai-engine.php
php -l wp-content/plugins/fftac-membership/inc/membership.php
' ' '
For theme tests:
' ' ' powershell
php tests/run.php
' ' '
For the full local sweep:
' ' ' powershell
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\test-theme.ps1
' ' '