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

Support

Support the Record

Support is for continuity, not reverence. It keeps the archive legible, the publication queue moving, and the public infrastructure resilient without pretending contribution buys doctrine or access to a sacred inner circle.

  • Classification Public support and underwriting brief
  • Access Public support route
  • Status Official public record under active editorial development
Route support through the contact desk Review the charter

Support File

FFTAC-SPT-01

Authority Explains how contributions support hosting, publication cadence, research buildout, and recovery-facing infrastructure without turning support into loyalty theater
Review Cycle Revised as funding priorities, live support tooling, and public operating costs change

Material support for a governed public record.

Support

Support the Record

Support exists to keep the public record alive, navigable, and durable. It is not tribute to a charismatic center, and it should never be confused with spiritual loyalty.

The Foundation is building a governed archive: doctrine, standards, dossiers, briefings, recovery pathways, and bounded AI inquiry. That kind of work needs material support, but the site should speak plainly about what support does and does not mean.

What Support Means Here

  • It helps sustain hosting, uptime, security posture, and public access.
  • It buys time for research, citation work, and careful publication rather than panic-content churn.
  • It supports recovery-facing routes, participation infrastructure, and future public events without turning the institution into a performance machine.
  • It does not buy doctrine, insider holiness, or immunity from criticism.

What We Refuse

We do not frame giving as righteousness, tithing as metaphysical duty, or donations as proof of alignment. Support should remain practical, proportionate, and visible in its purpose.

Before You Contribute

If you are not yet sure whether the Foundation’s posture fits your reasons for giving, read the charter, standards, research program, and recovery guide first. A serious institution should survive scrutiny before it ever asks to be materially backed.

Routing Status

Use this page to understand what support underwrites right now, how the Foundation thinks about money in public, and which routes fit small contributions, sustaining backing, or larger underwriting conversations.

A live payment link is not configured in this environment yet, so support currently routes through the contact desk until operations wiring is finalized.

Funding Priorities

What support funds right now

Priority 01

Hosting, edge protection, and uptime continuity

The first responsibility is keeping the public record reachable, fast, and resilient enough to survive launch traffic and ideological hostility.

Priority 02

Atlas buildout and citation-ready dossiers

Support buys time for claim files, chronology work, source verification, and the slower research labor that makes the archive worth citing.

Priority 03

Signals, journal releases, and editorial rhythm

Regular publication cadence matters because the institution earns trust by continuing to publish, revise, and document rather than by making grand static declarations.

Priority 04

Recovery-facing and participation infrastructure

Support also underwrites the public pathways that help readers move from panic and collapse toward slower reading, guided inquiry, and eventual contribution.

Impact Ledger

Visible public outputs the support layer is supposed to keep alive

These cards show the launch-time surfaces support is meant to protect and expand so the ask stays anchored to inspectable work instead of vague institutional glow.

Archive Continuity

Keep the public record reachable, navigable, and reproducible

Support first protects continuity: the site map, downloads, and public file stack need to stay reachable enough that the institution can survive scrutiny, sharing, and launch pressure.

Inspect the site map

Research Buildout

Extend the atlas, dossiers, and citation floor

Support buys time for claim dossiers, focused records, timeline maintenance, source verification, and the slower evidence work that makes the archive worth reopening and citing.

Inspect focused research records

Publication Rhythm

Sustain release cadence beyond launch-week enthusiasm

The journal and signals layer need ongoing editorial energy so FFTAC continues publishing, revising, and documenting rather than becoming a dramatic shell with no dependable cadence behind it.

Review the release sequence

Recovery Routes

Keep first-visit and recovery pathways humane

Support helps maintain the slower public routes that move readers out of panic, into contextual reading, and toward agency without forcing them into instant belonging.

Open recovery routes

Participation Infrastructure

Support the readiness layer beneath cohorts, contributors, and affiliates

Support also underwrites the intake, readiness, and protected workflow surfaces that let participation scale without collapsing back into generic membership theater.

Inspect the readiness desk

Support Lanes

Choose the support lane that fits

Launch Fund

One-time support for the public launch

Best for readers who want to back infrastructure, publication polish, and initial launch resilience without committing to an ongoing monthly rhythm.

Use this lane when you want a straightforward contribution tied to launch readiness rather than a recurring commitment.

Back the launch fund Inspect the live public stack

Sustaining Backer

Support the ongoing publication cadence

Best for readers who want to help underwrite recurring atlas updates, signals briefings, and the slower continuity work required after launch week passes.

Use this lane when your interest is continuity over spectacle and you want the archive to keep growing after the first attention spike fades.

Support the ongoing record Review the publication rhythm

Institutional Underwriting

Route larger support, sponsorship, or aligned backing

Best for partners, patrons, or institutions that need a human conversation about scope, timing, visibility, or launch-phase underwriting.

Use this lane when contribution questions are too specific for a generic payment flow and need actual human routing, timing, or visibility discussion.

Open the underwriting desk Review the public press packet

Public Orientation

Review the public record before contributing

Best for cautious readers who want to inspect doctrine, standards, and research posture before deciding whether support aligns with their reasons for giving.

Use this lane when trust still needs to be earned and you want to inspect the institution before money enters the picture.

Read the charter first Inspect the review log

Support Commitments

How money stays subordinate to the record

No tithing theater

Support is not framed as obedience, blessing, or proof of moral status. It is practical backing for practical work.

Money does not buy doctrine

Contributors may help sustain the record, but they do not purchase final authority over the philosophy, atlas, or editorial standards.

Public priorities over vague fundraising

Support asks should stay tied to visible operating needs such as hosting, publication, research buildout, and recovery-facing infrastructure.

Human route for larger backing

When support questions become complex, institutional, or deadline-sensitive, the contact desk should carry the conversation instead of hiding behind generic payment copy.