08 Research API And Programs - Source Excerpt 01 - Research API And Programs

Summary

This source excerpt begins near Research API And Programs and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/08-research-api-and-programs.md.
**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/08-research-api-and-programs.md
# Research API And Programs

This guide explains the current public data routes, generated exports, and program-intake flow.

## What Exists Now

The theme provides a repo-owned launch data layer:

- public read-only REST endpoints
- generated CSV, NDJSON, and TXT downloads
- stable record IDs for atlas records
- focused research-record URLs
- source records and claim-to-source links
- fact-check summary
- projection ledger for repeated claim history
- research connection map
- program board and public intake flow
- private WordPress storage for Signals signups, contact messages, and program inquiries
- admin-only CSV exports for Signals, Contact Desk, Program Intake, and combined launch-intake handoff
- Participants Database mirroring for operational roster work when that plugin is active
- admin-only launch handoff TXT export that summarizes readiness, proof gates, intake exports, machine routes, and remaining external work

This is implemented in `FFTAC Foundation Core`, with public rendering in the theme. It is not an external data platform yet.

## Public Site Surfaces

- Research API section:
  `template-research.php` at `#research-api`
- Research network:
  `template-research.php` at `#research-network`
- Projection ledger:
  `template-research.php` at `#projection-ledger`
- Focused record view:
  `template-research.php` at `#research-record`
- Export desk:
  `template-research.php` at `#export-desk`
- Downloads research export shelf:
  `template-downloads.php` at `#research-data-exports`
- HTML Site Map machine-route and focused-record sections:
  `template-sitemap.php`
- Join page program board, readiness desk, intake form, participation ladder, and output rhythm:
  `template-join.php`
- Membership portal member workflow:
  `template-membership-portal.php`
- Journal verified-research and contributor-lane routing:
  `template-journal.php`
- Internal launch intake operations:
  `Tools -> FFTAC Launch Readiness`
- Internal launch handoff packet:
  `Tools -> FFTAC Launch Readiness`
- Participants Database bridge and backfill:
  `Tools -> FFTAC Launch Readiness`

## Owning Files

- Copy, datasets, endpoint descriptions, and program definitions:
  `wp-content/plugins/fftac-foundation-core/inc/foundation-content.php`
- REST routes, generated exports, validation, storage, post types, and form handling:
  `wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- Private intake admin columns and CSV exports:
  `wp-content/plugins/fftac-foundation-core/inc/foundation.php`
- Research UI:
  `wp-content/themes/antichrist-engine/template-research.php`
- Downloads and machine-route discovery:
  `wp-content/themes/antichrist-engine/template-downloads.php`
  `wp-content/themes/antichrist-engine/template-sitemap.php`
- Join/program UI:
  `wp-content/themes/antichrist-engine/template-join.php`
- Member workflow:
  `wp-content/themes/antichrist-engine/template-membership-portal.php`
- Journal/publication context:
  `wp-content/themes/antichrist-engine/template-journal.php`
- Client-side filtering and URL sync:
  `wp-content/themes/antichrist-engine/assets/js/theme.js`
- Styling:
  `wp-content/themes/antichrist-engine/assets/css/theme.css`

## REST Namespace

Namespace:

`/wp-json/antichrist-engine/v1/`

## Research REST Routes

- `research`
  overview counts and route map
- `research/export`
  full Foundation Core-backed atlas payload
- `research/claims`
  claim dossiers with chronology entries, verdicts, evidence posture, source keys, and related records
- `research/timeline`
  timeline entries
- `research/projections`
  flattened projection-ledger entries derived from claim chronology
- `research/frameworks`
  framework map data
- `research/briefings`
  executive briefings
- `research/fact-check`
  verdict counts, evidence posture, chronology totals, and source totals
- `research/map`
  claim-to-source links, dossier bridges, source hubs, lane summaries, nodes, and edges
- `research/sources`
  source-library records and public URLs
- `research/series`
  publication-track metadata

## Governance REST Route

- `governance/review-notices`
  public review-notice register

## Supported REST Filters

Claims:

- `research/claims?category=church`
- `research/claims?q=temple`
- `research/claims?q=ai`

Timeline:

- `research/timeline?category=technology`

Projections:

- `research/projections?category=algorithmic`
- `research/projections?q=forecast`

Filter values are sanitized and validated in `wp-content/plugins/fftac-foundation-core/inc/foundation.php`. Short public search queries are capped at 120 characters.

## Generated Download Routes

Generated downloads are exposed through `fftac_download` query routes:

- `/?fftac_download=claims_csv`
- `/?fftac_download=timeline_csv`
- `/?fftac_download=projections_csv`
- `/?fftac_download=sources_csv`
- `/?fftac_download=records_ndjson`
- `/?fftac_download=provenance_txt`

These routes are surfaced on the Research page, Downloads page, and HTML Site Map.

## Research Page Query Parameters

The Research page supports shareable filters:

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

`record` opens a focused public record tied to a stable atlas ID such as `FFTAC-CLM-001`. Interactive filtering clears a focused record so the atlas can return to browse mode.

## Intake Storage

The theme stores public form submissions in private WordPress post types:

- `fftac_signal_signup`
  for Signals Briefing subscriptions
- `fftac_contact_message`
  for routed contact-desk messages
- `fftac_program_interest`
  for cohorts, summits, verified research, and affiliate/program inquiries

Signals signups are deduplicated by email.

Program inquiries are deduplicated by normalized email plus selected program slug.

Contact messages are not deduplicated because the same sender may submit different routed issues over time.

## Intake Operations Export

`Tools -> FFTAC Launch Readiness` includes admin-only CSV exports for:

- all launch intake
- Signals signups
- Contact messages
- Program inquiries

The export columns are stable across sources: intake source, post ID, status, submitted timestamp, name, email, lane, context, subject, message, and notes. Use these exports as the handoff format when records move into external newsletter, support, CRM, or program tooling.

The same admin page includes a launch handoff TXT export. That export is an operator packet: it summarizes launch visibility, readiness checks, final proof gates, private intake export links, machine-readable routes, and remaining external work. It does not make external services complete by itself.

When Participants Database is active, Foundation Core mirrors future Signals, Contact Desk, and Program Intake submissions into Participants Database. The local private post types remain the canonical audit trail; Participants Database is the roster-oriented working mirror. Existing records can be backfilled from `Tools -> FFTAC Launch Readiness`. See [14-participants-database-integration.md](14-participants-database-integration.md).