Skip to content
wiki.fftac.org

03 Theme Architecture - Source Excerpt 01 - Theme And Plugin Architecture

Back to 03 Theme Architecture

Summary

This source excerpt begins near Theme And Plugin Architecture and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/03-theme-architecture.md.

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

# Theme And Plugin Architecture

## Theme Root

Main path:

`wp-content/themes/antichrist-engine`

The theme now owns presentation: templates, assets, styles, client script, image-loading helpers, and post/template helpers. Application behavior lives in FFTAC plugins.

## Application Plugins

### Foundation Core

Main path:

`wp-content/plugins/fftac-foundation-core`

This required plugin loads:

- `inc/foundation-content.php`
- `inc/foundation.php`

It owns public data, page provisioning, routes, forms, exports, research API, search data, SEO, and launch readiness.

### AI Engine

Main path:

`wp-content/plugins/fftac-ai-engine`

This required plugin loads:

- `inc/ai-content.php`
- `inc/ai-engine.php`

It owns the signed-in AI console copy, personas, inquiry protocols, prompt lanes, command-map/response-contract/handoff surfaces, hidden server prompts, OpenAI site-key and user-key policy, AJAX handlers, response payloads, and output sharing. It depends on `FFTAC Foundation Core` for shared form/security helpers and page URL helpers.

### Membership

Main path:

`wp-content/plugins/fftac-membership`

This required plugin loads:

- `inc/membership.php`

It owns the front-end membership portal, account handlers, protected member page access, and member redirects. It depends on `FFTAC Foundation Core` for shared form/security helpers.

### Media Assets

Large public media files now live outside the theme in:

`wp-content/plugins/fftac-media-assets`

That plugin is a normal WordPress upload plugin. It supplies the bulky poster, wallpaper, preview, material-study, and press-kit files through the `antichrist_engine_foundation_asset` filter. The theme still owns the Downloads and Symbols page shells, the catalog metadata, the small seal/link-guide files, and generated research exports. If the media plugin is not active, the large media sections degrade away instead of breaking the page.

## Bootstrap

`functions.php` loads:

- `inc/template-tags.php`

It also checks that `FFTAC Foundation Core`, `FFTAC AI Engine`, and `FFTAC Membership` are active, registers theme support, menus, the sidebar, `assets/css/theme.css`, the compiled `assets/js/theme.js`, reusable image-loading helpers, WordPress attachment-image loading defaults, and localized JavaScript settings for the Research Navigator, launch visibility state, analytics event layer, and front-end interactions.

## Core Plugin Modules

### `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`

This is the main content and dataset file for the public site.

It owns:

- Foundation identity, document profiles, public assurances, offices, priorities, and official records
- Post-Dogmatic Humanism positioning, moral commitments, moral-method questions, philosophy voice standards, and final launch proof gates
- About public-thesis cards, Standards launch voice checks, expanded Q&A threshold answers, and editorial launch priorities
- manifesto, charter, standards, privacy, terms, community, and site-map default content, including launch-accurate policy language for intake storage, AI requests, analytics hooks, admin exports, and protected exchange
- research atlas datasets for frameworks, timelines, claim dossiers, source records, projection history, briefings, programs, and APIs
- review-notice register content
- recovery, texts, symbols, downloads, about, Q&A, contact, support, join, and journal copy
- publication-track definitions
- public download catalog, media-room packet data, and optional media-plugin collection metadata
- program blueprints, readiness packets, participation ladder, and output rhythm
- provisioned Foundation page definitions

Change default copy or dataset structure here first.

### `wp-content/plugins/fftac-foundation-core/inc/foundation.php`

This is the main application module for the public Foundation site.

It owns:

- versioned page provisioning and safe refresh of unchanged provisioned page bodies
- Foundation page ID/URL resolution and target URL helpers
- fallback navigation, topic map data, breadcrumbs, and page body classes
- site identity cleanup, starter-content cleanup, publication-category creation, and public archive helpers
- Research Navigator index and curated search scoring
- `Settings -> FFTAC Foundation` for launch visibility and the public support destination
- launch visibility mode, preview/private noindex controls, baseline security headers, internal launch readiness checks, go-live operations checklist, admin-only launch handoff TXT export, admin-only intake exports, SEO metadata, canonical/robots handling, social previews, virtual robots/sitemap discovery, and JSON-LD output
- review-notice register helpers and public governance route
- public REST routes under `antichrist-engine/v1`
- generated CSV, NDJSON, and TXT research export routes
- public form security helpers, nonce/timestamp/honeypot/rate-limit logic, and scalar/length-limited field reads
- private post types, admin columns, CSV exports, and handlers for Signals signups, contact messages, and program intake
- Participants Database bridge loading, FFTAC mirror-field provisioning, intake sync/backfill, readiness status, and launch-handoff reporting
- support destination resolution

Change routing, API behavior, public form behavior, search/discovery, launch indexing rules, security headers, readiness checks, or SEO here.

### `wp-content/plugins/fftac-foundation-core/inc/participants-database.php`

This file integrates the third-party Participants Database plugin without editing the plugin itself.

It owns:

- Participants Database availability detection
- FFTAC mirror-field definitions
- automatic sync for future Signals, Contact Desk, and Program Intake records
- admin-only backfill for existing intake
- readiness panel and launch handoff status