10 Launch Runbook

**Site relevance:** Anti-Christ.org

**Memory type:** docs archive

**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/10-launch-runbook.md

**Size:** 7.1 KB

Summary

This is the internal go-live sequence for anti-christ.org . It is not public site content.

Source Headings

Launch Runbook
Launch Principle
Theme And Plugin Controls
Go-Live Sequence
Stop Conditions
Roadmap Rule

Source Preview

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

# Launch Runbook

This is the internal go-live sequence for `anti-christ.org`. It is not public site content.

Use this file together with:

- [07-infrastructure-roadmap.md](07-infrastructure-roadmap.md)
- [deploy.md](deploy.md)
- `Settings -> FFTAC Foundation`, `Settings -> FFTAC AI Engine`, and `Settings -> FFTAC Membership` in WordPress admin
- `Tools -> FFTAC Launch Readiness` in WordPress admin

## Launch Principle

The theme and FFTAC plugins can prove that their own structure, forms, routes, exports, headers, and indexing switches are in place. They cannot replace human signoff for hosting, DNS, WAF, backups, analytics, email, payment, support triage, Search Console, first-post quality, or final rendered-page proofing.

Do not flip indexing to public just because the theme is technically ready. Flip indexing only when the production launch is intentionally discoverable.

## Theme And Plugin Controls

The theme and FFTAC plugins provide:

- preview/private/public launch visibility modes
- robots and `X-Robots-Tag` behavior tied to launch visibility
- baseline theme security headers
- public REST routes and generated research downloads
- private storage for Signals, Contact Desk, and Program Intake records
- admin-only CSV exports for private launch intake
- Standards page launch voice checks and final proof gates
- signed-in AI console with rendered command-map, response-contract, and handoff-route surfaces, fullscreen mode, safe rich/code output rendering, encrypted personal-key support, hidden persona/protocol controls, prompt-lane controls, follow-up prompt actions including research handoffs, session usage meters, browser-local workspace briefs, local transcript copy/export/import, JSON and Markdown transcript exports, local session snapshots, Foundation-key cost limits, and explicit output-to-post sharing
- plugin settings pages for Foundation launch/support settings, AI key/model/flavor settings, and Membership page selectors
- optional `FFTAC Media Assets` plugin for large poster, wallpaper, preview, material-study, and press-kit files
- `Tools -> FFTAC Launch Readiness` checks
- admin-only launch handoff TXT export
- deploy zips through `scripts/build-deploy-zips.ps1`

## Go-Live Sequence

1. Review source state.

Run `git status --short` and make sure pending changes are understood. Do not ship unknown edits.

2. Run the local quality sweep.

' ' ' powershell
php tests/run.php
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\test-theme.ps1
' ' ' 

3. Open the admin readiness page.

In WordPress admin, open `Tools -> FFTAC Launch Readiness`.

Use it to inspect:

- launch visibility and WordPress search visibility
- provisioned Foundation pages
- private intake storage
- intake export readiness
- research API and generated download routes
- security headers
- support destination
- AI key state, including the Foundation key saved in `Settings -> FFTAC AI Engine`, and Foundation-key cost posture
- analytics event hooks
- go-live operations checklist

Download the launch handoff TXT before production promotion.

4. Export private launch intake.

From the same admin page, export:

- all launch intake
- Signals signups
- Contact Desk messages
- Program Intake records

Use these CSV files as the handoff into external newsletter, support, CRM, or program tools. The theme-stored records are the prelaunch bridge, not the permanent operating system.

5. Run the Standards final proof gates.

Open the Standards page and use `Final Proof Gates` before promotion:

- first-contact explanation
- recovery safety
- evidence and research trail
- AI boundary
- intake and support handoff
- publication readiness
- governance and amendment trail

This is the final human proofing layer for public language. It should happen after provisioning, admin edits, and first posts are in place.

6. Confirm external operations.

Before public indexing, confirm owners and settings for:

- production hosting, DNS, SSL, CDN/reverse proxy, WAF, and DDoS posture
- backups and a tested restore path
- uptime checks, error monitoring, and log review
- privacy-aware analytics, Search Console, sitemap submission, and launch dashboard
- email/newsletter deliverability
- contact/support/program triage outside WordPress if needed
- payment or donation tooling if support should route somewhere other than the contact fallback

7. Build deploy packages.

' ' ' powershell
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\build-deploy-zips.ps1
' ' ' 

Use:

- `E:\antichristorg-Publish` for WordPress theme upload
- `E:\antichristorg-Plugin-Publish` for the Foundation Core, AI Engine, Membership, and Media Assets plugin uploads when the plugins are not installed or their payload changes
- `Releases\` only for full-site server deployment

8. Confirm indexing intentionally.

Confirm launch visibility is `public` in `Settings -> FFTAC Foundation`. The theme defaults to `public`; staging and hidden environments should override `ANTICHRIST_ENGINE_LAUNCH_VISIBILITY`, the matching environment variable, or the `antichrist_engine_launch_visibility` option to `preview` or `private`.

Then confirm WordPress `Settings -> Reading -> Search Engine Visibility` is not discouraging indexing.

9. Verify after launch.

After deploy and indexing changes:

- check Home, Manifesto, About, Philosophy, Research, Recovery, AI Engine, Join, Journal, Standards, policies, Contact, Support, Downloads, and Site Map
- check the `FFTAC Media Assets` plugin is active before expecting poster, wallpaper, material-study, preview, and press-kit downloads to appear
- check that AI Engine guests see the account gate and signed-in users see the AJAX console, rendered command-map/prompt-lane/response-contract/handoff sections, richer flavor deck, inquiry protocol deck, follow-up prompt actions including research handoffs, fullscreen toggle, formatted/code output rendering, local history, workspace brief panel, session usage meters, transcript copy/JSON export/Markdown export/import controls, local session snapshot controls, personal-key panel, and output sharing controls
- check `/robots.txt`
- check `/wp-sitemap.xml`
- check key REST routes under `/wp-json/antichrist-engine/v1/`
- check generated `fftac_download` links
- submit the sitemap in Search Console when ready
- confirm analytics events are being received if an analytics provider is connected

## Stop Conditions

Stop before promotion if:

- a readiness check is blocked
- the launch handoff TXT names unresolved external work with no owner
- the final proof gates reveal domain, recovery, AI, evidence, support, or governance copy that creates confusion
- Search Console, sitemap submission, DNS, backups, or rollback ownership are not ready but public indexing is being considered
- the wrong zip type is about to be uploaded

## Roadmap Rule

Do not move external operational work into "completed" just because the theme exposes a checklist or export. A roadmap item is complete only when the production dependency is configured, documented, owned, and tested.