Skip to content
wiki.fftac.org

01 Start Here

**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/01-start-here.md

**Size:** 7.4 KB

Summary

This is the full WordPress site for anti-christ.org .

Source Headings

  • Start Here
  • What This Repo Is
  • Current Baseline
  • What To Read Next
  • Local Setup
  • Project Layout
  • Important Rules
  • Main Source Files

Source Preview

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

# Start Here

## What This Repo Is

This is the full WordPress site for `anti-christ.org`.

The custom work is split between the `Antichrist Engine` presentation theme and FFTAC-owned plugins:

- provisioned public Foundation pages
- homepage moral-center framing, About public-thesis cards, Post-Dogmatic Humanism philosophy hub, moral-commitment framework, launch voice checks, and final proof gates
- research atlas, public API, generated exports, source records, and focused record views
- signed-in AJAX AI inquiry console with rendered command-map, response-contract, and handoff-route surfaces, fullscreen mode, prompt-lane controls, distinct personality flavors, inquiry protocols, follow-up prompt actions including research handoffs, session usage meters, browser-local workspace briefs, transcript copy/export/import, JSON and Markdown transcript exports, local session snapshots, safe rich/code output rendering, personal-key support, and explicit output-to-post sharing
- recovery, texts, symbols, journal, downloads, support, contact, public policy, and governance surfaces
- front-end membership portal and protected members area
- launch forms for Signals signups, contact messages, and program intake, with admin-only intake review/export tools
- preview-safe launch visibility controls, Foundation/AI/Membership admin settings pages, baseline security headers, media-loading defaults, reduced-motion safeguards, an internal launch readiness page with a go-live checklist and launch handoff TXT export, and client-side event hooks for later analytics wiring

`FFTAC Foundation Core` owns the public data, provisioning, research API, forms, launch readiness, and SEO. `FFTAC AI Engine` owns the signed-in AI console data, personas, protocols, OpenAI key policy, AJAX handlers, and output sharing. `FFTAC Membership` owns the front-end account layer. Large public media files live in the optional `FFTAC Media Assets` WordPress plugin at `wp-content/plugins/fftac-media-assets` so routine theme uploads stay small.

## Current Baseline

The site is no longer a blank rebuild plan. The theme plus FFTAC plugins already provide the core public structure, Post-Dogmatic Humanism positioning, About public-thesis cards, Standards launch voice checks and final proof gates, expanded Doctrine Q&A, search/discovery systems, public data surfaces, participation intake layer, launch-accurate public privacy/terms/community defaults, admin-only intake exports, launch visibility controls, baseline security headers, media-loading defaults, reduced-motion safeguards, an internal launch readiness page with launch handoff export, and a client-side analytics event layer.

Future planning should focus on work outside the current theme/plugin baseline: hosting and edge protection, security operations, analytics, external email/payment tooling, editorial operations, partnerships, translations, and any later data layer that replaces plugin-backed arrays.

## What To Read Next

1. [02-site-map.md](02-site-map.md) for the page and route structure
2. [03-theme-architecture.md](03-theme-architecture.md) for the file map
3. [04-membership-system.md](04-membership-system.md) for login and protected access
4. [05-editing-guide.md](05-editing-guide.md) for the fastest route to the owning file
5. [06-strategy-research.md](06-strategy-research.md) for strategy status and archived memo context
6. [07-infrastructure-roadmap.md](07-infrastructure-roadmap.md) for future operational work
7. [08-research-api-and-programs.md](08-research-api-and-programs.md) for public data endpoints and program intake
8. [09-discoverability-and-search.md](09-discoverability-and-search.md) for navigator, search, breadcrumbs, SEO, and structured data
9. [10-launch-runbook.md](10-launch-runbook.md) for the go-live sequence and stop conditions
10. [11-user-ai-architecture.md](11-user-ai-architecture.md) for the signed-in AI console, fullscreen/rich output behavior, local session tools, personal keys, hidden personas/protocols, follow-up sharing, and AJAX routes
11. [deploy.md](deploy.md) for release packaging

## Local Setup

1. Copy `wp-config-sample.php` to `wp-config.php`.
2. Add database credentials, salts, and local host settings in `wp-config.php`.
3. Serve `E:\antichristorg` with a local PHP/MySQL stack.
4. Open `/wp-admin/install.php` if WordPress is not installed yet.
5. Activate `FFTAC Foundation Core`, `FFTAC AI Engine`, `FFTAC Membership`, and then the `Antichrist Engine` theme. Activate `FFTAC Media Assets` when the large download payload should be available.
6. Use `Settings -> FFTAC Foundation` for launch visibility and the public support destination. Launch visibility defaults to `public`; set `ANTICHRIST_ENGINE_LAUNCH_VISIBILITY`, the hosting environment variable, or the saved option to `preview` or `private` only for staging, review, or intentionally hidden environments.
7. Use `Settings -> FFTAC AI Engine` for the Foundation OpenAI key, model/defaults, and editable response-flavor deck.
8. Use `Settings -> FFTAC Membership` if the membership portal or members-area pages need to point at replacement pages.
9. Use `Tools -> FFTAC Launch Readiness` in WordPress admin for the internal prelaunch state check, go-live operations checklist, intake CSV exports, and launch handoff TXT export.

## Project Layout

- WordPress root:
  `E:\antichristorg`
- WordPress theme-upload output:
  `E:\antichristorg-Publish`
- WordPress plugin-upload output:
  `E:\antichristorg-Plugin-Publish`
- Full-site release packages:
  `Releases\`
- Custom theme:
  `wp-content/themes/antichrist-engine`
- Foundation core plugin:
  `wp-content/plugins/fftac-foundation-core`
- AI engine plugin:
  `wp-content/plugins/fftac-ai-engine`
- Membership plugin:
  `wp-content/plugins/fftac-membership`
- Media assets plugin:
  `wp-content/plugins/fftac-media-assets`
- Documentation:
  `docs\`
- Tests:
  `tests\`
- Launch runbook:
  `docs\10-launch-runbook.md`
- User AI architecture:
  `docs\11-user-ai-architecture.md`

## Important Rules

- Do not start by editing WordPress core.
- Do not treat the old dated strategy memos as active roadmaps.
- Do not re-add theme or FFTAC plugin features that already exist to the future roadmap.
- Treat Markdown files as internal documentation and instructions, not public site files.
- Keep source edits 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 Foundation Core, AI Engine, Membership, and the large media payload.

## Main Source Files

- Theme bootstrap:
  `wp-content/themes/antichrist-engine/functions.php`
- Public content and datasets:
  `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`
- Page provisioning, routes, API, forms, search, SEO, and launch helpers:
  `wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- AI console data, key policy, AJAX, and sharing:
  `wp-content/plugins/fftac-ai-engine`
- Membership flow:
  `wp-content/plugins/fftac-membership/inc/membership.php`
- Shared post/publication helpers:
  `wp-content/themes/antichrist-engine/inc/template-tags.php`
- Styling:
  `wp-content/themes/antichrist-engine/assets/css/theme.css`
- Front-end behavior:
  source `wp-content/themes/antichrist-engine/assets/ts/theme.ts`
  compiled output `wp-content/themes/antichrist-engine/assets/js/theme.js`
Website health report