Designation FFTAC independent public philosophy and research foundation

Status Official public record with stable canonical files

Method Editorial governance, adversarial inquiry, long-form publication

Foundation For The Anti-Christ

Canonical files, governed publication, and machine-assisted inquiry for the post-dogmatic age.

FFTAC / Independent Public Philosophy and Research Foundation FFTAC-REC-00 Founding public edition
Official Record Support the Record

Public Contact

Contact

The contact desk exists to route serious correspondence without collapsing research corrections, recovery questions, media requests, and public feedback into one vague inbox.

  • Classification Public correspondence desk
  • Access Public intake with private editorial review
  • Status Official public record under active editorial development
Open Contact Desk Program Intake

Contact File

FFTAC-CNT-01

Authority Routes launch-facing questions, research corrections, recovery orientation, and media requests into the right working lane
Review Cycle Revised as contact routes, public operations, and launch workflows mature

Structured intake. Human review. No prophecy hotline theatrics.

Contact

Contact

The Contact desk is the Foundation’s public routing layer for serious correspondence: research corrections, media requests, recovery-oriented questions, program uncertainty, and launch-critical site issues.

A public institution needs a way to be reachable without becoming an unstructured inbox. This page exists to help readers, journalists, collaborators, and cautious newcomers reach the right lane with enough context that a human reviewer can act proportionally.

What Belongs Here

  • Research corrections, citation disputes, and source additions tied to specific dossiers or pages.
  • Media, speaking, partnership, or directory requests connected to the public launch.
  • Program-routing questions when you are unsure whether the Join page or portal pathways fit you.
  • Recovery-oriented orientation questions from readers leaving fear-based religion who need the right public starting point.
  • Site bugs, broken links, accessibility friction, or public API issues that block access to the record.

What Helps Us Respond Well

Specificity matters more than volume. If you include the page URL, claim name, source title, deadline, publication context, or technical steps needed to reproduce a problem, the message becomes easier to route and far easier to answer responsibly.

Boundaries

This institution is not a crisis line, therapy provider, church discipline office, or prophecy hotline. It can publish, critique, route, and correspond; it should not pretend to be a substitute for emergency care, licensed services, or direct pastoral authority.

If your question is primarily about joining a cohort, summit, or contributor lane, the dedicated intake system on the Join page is still the fastest structured route. The contact desk is for messages that need human routing before they fit an obvious lane.

Route Map

Choose the desk before you write

Each route is tuned for a different kind of launch-time correspondence so the public inbox does not become a fog machine for corrections, press, orientation, and bug reports.

Editorial Desk

Public questions, reader notes, and general correspondence

Use this route for public-facing questions about FFTAC, site structure, launch context, or where a new reader should begin.

Best when you need orientation, clarification, or a human routing decision before the issue belongs in a narrower desk.

Best default if you are not yet sure which lane fits.

Use this route Review the institutional brief Scan the doctrine Q&A

Research Desk

Citations, factual corrections, source leads, and dossier disputes

Use this lane when a claim file, timeline note, or source trail needs correction, stronger evidence, or a missing counter-reading.

Best when the message is evidentiary and can be checked against a claim dossier, timeline entry, projection ledger record, or source file.

Include URLs, publication details, timestamps, or exact claim references whenever possible.

Use this route Open focused records Review the source library

Press Desk

Interviews, speaking requests, directory listings, and external collaborations

Use this route for press contacts, podcasters, conference organizers, research collaborators, or partners evaluating the public launch.

Best when another outlet, organizer, or institution needs a public-facing packet, timeline, quote, interview, or collaboration conversation.

Deadlines, audience context, and expected deliverables help this lane move faster.

Use this route Review the press kit Open the flagship AI track

Participation Desk

Questions about cohorts, summits, affiliates, or contributor pathways

Use this route when you need help deciding whether the Join page, portal, or a specific program lane fits your background or goals.

Best when you need lane selection help before submitting an intake note or when your background crosses multiple participation routes.

If you already know the lane, the program intake form remains the faster path.

Use this route Open the program intake board Review the readiness desk

Recovery Desk

Questions from readers leaving panic theology or control-heavy systems

Use this route if you need help finding the most appropriate public entry point for recovery, slower study, or post-religious reconstruction.

Best when fear-based religion, prophecy panic, or coercive doctrine are still emotionally live and you need the least destabilizing public route first.

The Foundation is not a crisis service, but it can route readers toward the most relevant public materials.

Use this route Open the recovery guide Open recovery answers

Operations Desk

Broken links, form problems, accessibility friction, or research API issues

Use this route for launch bugs, navigation friction, feed problems, or issues that block access to the public record.

Best when something on the public site fails in a repeatable way and a maintainer will need steps, environment details, and a page reference to reproduce it.

Please include device, browser, page URL, and the exact failure if you can.

Use this route Review the public site map Review the public API

Message Packets

Build the smallest useful packet

The best routed messages arrive with enough context to move. These packet cards tell you what to include so the desk can respond proportionally instead of guessing.

General editorial

Public questions, reader notes, and general correspondence

Best when you need orientation, clarification, or a human routing decision before the issue belongs in a narrower desk.

  • The page, file, or decision point creating the question.
  • What you are trying to understand, request, or confirm.
  • Any deadline or public context that changes response priority.
Send through this desk Scan the doctrine Q&A

Research corrections and sources

Citations, factual corrections, source leads, and dossier disputes

Best when the message is evidentiary and can be checked against a claim dossier, timeline entry, projection ledger record, or source file.

  • The exact claim, record ID, page URL, or source record under dispute.
  • The citation, scan, URL, timestamp, or edition that supports your correction.
  • A concise explanation of what is wrong, missing, or framed too loosely.
Send through this desk Review the source library

Media, press, and partnerships

Interviews, speaking requests, directory listings, and external collaborations

Best when another outlet, organizer, or institution needs a public-facing packet, timeline, quote, interview, or collaboration conversation.

  • The outlet, organization, event, or directory making the request.
  • Deadline, audience size, format, and expected deliverable.
  • Any preferred angle, publication context, or flagship topic lane.
Send through this desk Open the flagship AI track

Programs and participation

Questions about cohorts, summits, affiliates, or contributor pathways

Best when you need lane selection help before submitting an intake note or when your background crosses multiple participation routes.

  • What kind of participation you are considering and why now.
  • Relevant background, discipline, or publication context.
  • Whether you need a public route, a slower protected workflow, or just orientation.
Send through this desk Review the readiness desk

Recovery and orientation

Questions from readers leaving panic theology or control-heavy systems

Best when fear-based religion, prophecy panic, or coercive doctrine are still emotionally live and you need the least destabilizing public route first.

  • The panic script, doctrine, or environment you are trying to exit.
  • Whether you want reading routes, question routing, or slower participation guidance.
  • Any boundaries that would help keep the exchange proportionate and non-retraumatizing.
Send through this desk Open recovery answers

Site bug or accessibility issue

Broken links, form problems, accessibility friction, or research API issues

Best when something on the public site fails in a repeatable way and a maintainer will need steps, environment details, and a page reference to reproduce it.

  • The exact page URL, endpoint, or form involved.
  • Device, browser, accessibility tooling, or environment details.
  • The failure steps, error text, or expected behavior versus actual behavior.
Send through this desk Review the public API

Contact Desk

Send a routed message into the Foundation

If you are unsure which route fits, choose the closest lane and be concrete. Messages with deadlines, URLs, citations, or exact page references are much easier to route well.

Press Desk

Interviews, speaking requests, directory listings, and external collaborations

Use this route for press contacts, podcasters, conference organizers, research collaborators, or partners evaluating the public launch.

Deadlines, audience context, and expected deliverables help this lane move faster.

Messages are stored privately inside WordPress for editorial routing and follow-up. This is not live chat, therapy, legal advice, or emergency support.

Response Protocol

How the contact layer stays useful during launch pressure

Routing over spectacle

The contact layer exists to sort messages into the right desk rather than turning every incoming note into vague public theater.

Specificity beats intensity

Deadlines, citations, URLs, and exact page references are more useful than declarations of urgency without context.

No pastoral or emergency promises

FFTAC is a philosophy and research institution, not a therapy provider, crisis line, or prophecy hotline.

Private intake, proportional follow-up

Messages are stored privately for editorial review and routed proportionally rather than harvested for decorative community metrics.