09 Discoverability And Search - Source Excerpt 01 - Discoverability And Search

Summary

This source excerpt begins near Discoverability And Search and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/09-discoverability-and-search.md.
**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/09-discoverability-and-search.md
# Discoverability And Search

This guide covers the tools that help people find the right page, record, source, program, or publication quickly.

## What Exists Now

The theme and `FFTAC Foundation Core` currently provide:

- global Research Navigator overlay in the header
- keyboard shortcuts: `Ctrl + K`, `Cmd + K`, and `/` when not typing
- global breadcrumbs
- global topic map
- homepage and research-page Research Command surfaces
- shareable research filters
- shareable focused research-record views
- projection-ledger filters
- research-network filters
- stable atlas record IDs
- generated research export links
- custom search page with curated navigator matches before raw WordPress results
- custom `searchform.php`
- reader-type routing on homepage, About, search, navigator, and site map
- moral-center route, About public-thesis cards, launch desk, Standards voice checks and final proof gates, Q&A decision routes, contact packets, support routes, media-room packets, publication packets, and program/workflow routes
- dedicated HTML Site Map
- footer governance and discovery links
- AI Engine command-map, prompt-lane, response-contract, and handoff-route sections that keep the signed-in console discoverable without requiring a live prompt first
- SEO metadata, canonical and robots handling, preview-safe launch visibility controls, baseline security headers, social previews, sitemap discovery in virtual `robots.txt`, and structured data
- focused research-record URLs exposed through the WordPress XML sitemap index as a custom sitemap provider
- client-side `antichrist:analytics` events for search, navigator, downloads, support, forms, AI console interactions, research filters, and focused record views

## Owning Files

- Navigator data, breadcrumbs, SEO, structured data, robots/canonical policy, sitemap discovery, social previews, and curated search scoring:
  `wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- Navigator labels and localized data:
  `wp-content/themes/antichrist-engine/functions.php`
- Header overlay, topic map, and breadcrumb placement:
  `wp-content/themes/antichrist-engine/header.php`
- Homepage discovery routes and command surface:
  `wp-content/themes/antichrist-engine/front-page.php`
- Research filters, focused records, network explorer, and command deck:
  `wp-content/themes/antichrist-engine/template-research.php`
- Search results page:
  `wp-content/themes/antichrist-engine/search.php`
- Shared search form:
  `wp-content/themes/antichrist-engine/searchform.php`
- HTML Site Map and footer discovery:
  `wp-content/themes/antichrist-engine/template-sitemap.php`
  `wp-content/themes/antichrist-engine/footer.php`
- Destination templates:
  `template-about.php`, `template-ai-engine.php`, `template-contact.php`, `template-downloads.php`, `template-governance.php`, `template-join.php`, `template-journal.php`, `template-questions.php`, `template-recovery.php`, `template-review-notices.php`, `template-standards.php`, `template-support.php`, `template-symbols.php`, `template-texts.php`
- Large media payload for poster, wallpaper, preview, material-study, and press-kit routes:
  `wp-content/plugins/fftac-media-assets`
- Client-side behavior:
  source `wp-content/themes/antichrist-engine/assets/ts/theme.ts`
  compiled output `wp-content/themes/antichrist-engine/assets/js/theme.js`
- Styling:
  `wp-content/themes/antichrist-engine/assets/css/theme.css`

## How The Navigator Is Fed

The curated navigator index is built by `antichrist_engine_foundation_get_navigator_index()` in `wp-content/plugins/fftac-foundation-core/inc/foundation.php`.

It pulls from:

- key provisioned pages
- moral center, About public-thesis cards, and Standards route/check records
- Standards final proof gates for go-live proofing, recovery safety, AI boundaries, intake handoff, and governance signoff
- reader-type routes
- launch desk routes
- doctrine Q&A routes
- contact routes
- support impact and support-lane routes
- media-room routes and briefing packets
- downloads, optional media-plugin assets, and research export routes
- review notices
- texts reading routes and case files
- symbols lexicon entries and material studies
- executive briefings
- timeline entries
- claim dossiers
- source records
- projection-ledger entries
- research command presets
- research connection-map records
- journal series, release-desk routes, and publication packets
- program options, readiness packets, and member workflow items
- recent published posts

Navigator records include titles, summaries, URLs, type/group labels, metadata, record IDs, and keyword strings. That lets users search by citation handle, job to be done, audience need, route name, source, or ordinary phrase.

## Search Layers

There are two search layers:

1. Research Navigator:
   curated high-signal destinations.
2. WordPress search:
   broader posts/pages index.

`search.php` shows navigator-style matches first, then normal WordPress results.

The search surface is designed to understand terms such as:

- `algorithmic eschatology`
- `ask the adversary`
- `verified research`
- `former believer`
- `press inquiry`
- `underwriting`
- `media room`
- `briefing packet`
- `claims csv`
- `provenance note`
- `release desk`
- `citation dossier`
- `FFTAC-CLM-001`

## Research Query Parameters

The Research page supports:

- `claim_q`
- `claim_category`
- `claim_verdict`
- `timeline_category`
- `projection_q`
- `projection_category`
- `map_q`
- `map_kind`
- `map_category`
- `record`

The server renders the selected state on first load. JavaScript keeps interactive filtering and copied URLs in sync.

## Structured Data And Indexing

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

- organization graph
- website graph and `SearchAction`
- page-specific `WebPage` data
- breadcrumb structured data
- Doctrine Q&A `FAQPage`
- `ItemList` graphs for major launch surfaces
- research atlas `Dataset`
- single publication structured data
- canonical URLs
- selective noindex behavior plus launch visibility modes
- virtual `robots.txt` sitemap discovery
- a custom XML sitemap provider for focused `?record=FFTAC-*` research-record URLs
- page-specific social descriptions and images
- Open Graph image dimensions and article timing metadata when available

Launch visibility modes:

- `preview`: review mode; pages stay browsable but search indexing is blocked with noindex directives and an `X-Robots-Tag` header.
- `private`: blocks indexing and following when the environment should not invite crawler traversal.
- `public`: default launch mode; allows indexable views to be indexed when WordPress Search Engine Visibility is also enabled.

Set launch visibility through `Settings -> FFTAC Foundation`, the `ANTICHRIST_ENGINE_LAUNCH_VISIBILITY` constant, the matching environment variable, or the `antichrist_engine_launch_visibility` option to override the default public mode. Search results, 404s, previews, feeds, transient form-status URLs, and duplicate research-filter query views remain noindex even in `public` mode. Valid focused research-record URLs remain indexable and canonical.

Baseline security headers are also sent from `wp-content/plugins/fftac-foundation-core/inc/foundation.php`. They are visible in the internal `Tools -> FFTAC Launch Readiness` page together with indexing, page provisioning, form storage, admin-only intake exports, launch handoff export, research route, support, AI, and analytics-hook checks.

## Analytics Event Layer

`assets/js/theme.js` dispatches a browser event named `antichrist:analytics` and pushes the same payload to `window.dataLayer` if a data layer exists. This gives the future analytics stack stable event names without placing provider code in templates.

Current event names:

- `navigator_opened`
- `navigator_search_used`
- `navigator_result_selected`
- `navigator_full_search_opened`
- `site_search_submitted`
- `research_command_submitted`
- `research_filter_changed`
- `focused_research_record_viewed`
- `signals_signup_submitted`
- `contact_message_submitted`
- `program_interest_submitted`
- `ai_prompt_submitted`
- `ai_response_received`
- `ai_prompt_error`
- `ai_persona_changed`
- `ai_protocol_changed`
- `ai_protocol_selected`
- `ai_prompt_lane_loaded`
- `ai_followup_loaded`
- `ai_workspace_brief_saved`
- `ai_workspace_brief_applied`
- `ai_workspace_brief_cleared`
- `ai_history_cleared`
- `ai_key_saved`
- `ai_key_removed`
- `ai_key_error`
- `ai_fullscreen_toggled`
- `ai_output_copied`
- `ai_output_shared`
- `ai_output_share_error`
- `ai_transcript_exported`
- `ai_transcript_markdown_exported`
- `ai_transcript_copied`
- `ai_transcript_imported`
- `ai_transcript_import_error`
- `ai_session_snapshot_saved`
- `ai_session_snapshot_restored`