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

Post-Dogmatic Humanism, governed publication, and machine-age inquiry for the age of counterfeit authority.

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

Editorial Standards

Editorial Standards

The standards file turns tone, evidence, machine use, publication, and amendment discipline into a visible operating surface before the archive goes fully public.

  • Classification Editorial policy
  • Access Public record
  • Status Official public record under active editorial development
Open the standards map Open review notices

Standards File

FFTAC-STD-01

Public assurances 4
AI protocols 4
Proof gates 7
Promotion stages 4

Calm register. Visible sources. Bounded machine use. Promotion by review instead of drift.

Operating File

Editorial Standards

The Foundation publishes under standards designed to preserve seriousness, interpretive integrity, and institutional discipline.

Tone and Register

Writing should remain calm, exact, lucid, and literate. Empty provocation, theatrical blasphemy, internet edginess, and adolescent inversion are treated as failures of thought, not signs of courage.

Public Voice Test

Every major public surface should make a wounded, thoughtful, skeptical stranger feel more grounded, more respected, and more capable of thinking clearly. If a page mainly produces contempt, recruitment pressure, or rhetorical intoxication, it has failed the philosophy even when the argument is sharp.

Launch Readiness Rule

Before a public file is treated as launch-ready, it should pass the Foundation’s voice checks: the target is counterfeit authority rather than believers, the moral center is visible before critique escalates, recovery readers are protected from contempt, AI remains bounded, and support is tied to visible work rather than loyalty pressure.

Interpretive Discipline

  • Critique systems before persons.
  • Explain the structure before condemning the failure.
  • Keep critique aimed at doctrines, institutions, technologies, incentives, and claims rather than protected identities.
  • Differentiate symbolic, philosophical, literary, theological, and historical claims clearly.
  • State confidence proportionally and avoid absolutist language the argument cannot support.
  • Do not use the Anti-Christ as a license for hatred, cruelty, or spectacle.

Moral Method

Editorial judgment begins with dignity, truth, freedom, repair, and responsibility. Claims should be tested by asking who is harmed, who benefits, who is silenced, what evidence supports the claim, whether consent is real, whether repair is possible, and whether the rule would still seem just if applied to us.

Evidence Posture

When a text makes historical, theological, or comparative claims, sources and context should be clear enough for readers to follow the reasoning. Citation is a tool of seriousness, not compliance theater.

AI Governance

AI may be used to pressure assumptions, compare frames, and draft philosophical alternatives. It may not be treated as a prophet, final authority, or substitute for editorial judgment. Machine output remains provisional until reviewed, revised, and situated inside the Foundation’s record.

Promotion Rule

Canonical pages should remain stable, versioned, and internally coherent. Experimental work belongs in the Journal, submissions layer, or AI engine until it earns promotion into the official record.

Standards Map

The standards map

Use this file when you need to understand how institutional posture, publication rules, AI boundaries, and amendment pressure fit together instead of reading them as disconnected policies.

Posture

Start with the non-negotiable assurances

Read the rules that keep participation voluntary, critique institutional, AI bounded, and canonical files stable enough to cite.

Open the posture layer

Voice

Run the prelaunch public-voice check

Make sure the site explains the domain, moral center, recovery posture, AI boundary, support ask, and contributor invitation before critique becomes noisy.

Open voice checks

Proof

Use the final proof gates before promotion

Convert launch voice standards into concrete checks for first-contact copy, recovery safety, evidence posture, intake handoff, and publication readiness.

Open proof gates

Archive

See how publication and verification interact

Track the difference between ordinary archive release, verified research review, and the slower movement into canonical status.

Inspect the archive pipeline

Machine

Review the AI governance contract

The AI Engine can help pressure assumptions, but it stays under the same editorial discipline as every other public surface.

Review AI boundaries

Promotion

Follow the path from draft to canon

Ideas should move through testing, publication, verification, and review rather than being promoted by excitement alone.

Trace the promotion ladder

Review

Keep cadence tied to visible amendment pressure

Signals, journal releases, directorate reviews, and formal notices are meant to keep archive growth answerable to the public record.

Open the review cadence

Institutional Posture

Institutional posture before publication

These assurances keep the Foundation from reenacting the panic, coercion, and theatrical certainty it critiques elsewhere.

Voluntary participation remains primary

No page, office, tool, or doctrine compels allegiance. Participation begins and ends with individual conscience.

Critique remains institutional

The Foundation examines doctrines, texts, symbols, systems, and institutions without authorizing persecution of persons or protected groups.

AI remains bounded by editorial governance

Machine output may provoke, compare, and clarify, but it does not become prophecy, law, revelation, or final interpretation.

Canonical files remain stable and citable

Manifesto, charter, research, and standards are maintained as public files suitable for citation, challenge, and formal amendment.

Launch Voice Checks

Launch voice checks

Every prominent public page should pass these checks before promotion, outreach, or citation pressure makes the first impression harder to revise.

Check 01

Explain the name as a counterfeit-authority critique

A launch reader should understand quickly that Anti-Christ names resistance to sacred, political, cultural, and algorithmic power that refuses accountability.

Revise any copy that sounds like an anti-believer campaign or protected-identity attack.

Check 02

Put the moral center before the heat

Free conscience, dignity, truth, repair, responsibility, embodied flourishing, and pluralistic courage should be visible before the archive asks readers to follow a hard critique.

A sharp page still needs to show what it protects, not only what it opposes.

Check 03

Protect recovery readers from contempt

Readers leaving fear-based religion should meet orientation, permission to slow down, and practical routes rather than humiliation for what once held them.

No recovery-facing page should trade one domination script for another.

Check 04

Keep AI bounded before using AI publicly

Machine-assisted inquiry may pressure assumptions and compare frames, but it must never inherit the voice of prophet, priest, judge, oracle, or final authority.

If the machine sounds like command, revelation, or certainty theater, lower its authority.

Check 05

Make evidence and uncertainty visible

Claims should show their source posture, confidence level, and counter-reading awareness so seriousness is earned rather than performed through tone.

Strong rhetoric cannot substitute for a visible path back to evidence.

Check 06

Tie support and contribution to real work

Support, membership, and contributor language should stay voluntary, practical, and tied to visible outputs instead of implying loyalty, salvation, status, or insider holiness.

Contribution should feel like stewardship of a public record, not identity performance.

Final Proof Gates

Final proof gates before promotion

These gates turn the launch voice standard into concrete page, route, and handoff checks so final proofing can happen without guessing what readiness means.

Gate 01

First-contact explanation

A stranger can explain what the name means without turning it into an attack on believers

Test
Read Home, About, Manifesto, and Q&A as if this is the first encounter with the domain.
Pass condition
The target is counterfeit authority, the moral center appears before critique escalates, and no protected identity is made into the enemy.
Owner
Editorial proof
Proof the public thesis

Gate 02

Recovery safety

A frightened or recently deconstructing reader gets orientation instead of more panic

Test
Read Recovery, AI Engine examples, reader routes, and contact language through a high-anxiety lens.
Pass condition
The page slows the reader down, avoids contempt, names practical next steps, and never replaces one domination script with another.
Owner
Recovery proof
Proof recovery routes

Gate 03

Evidence and research trail

Every strong claim can point back to a record, source posture, or export route

Test
Check Research, Downloads, Site Map, and any launch essay that makes historical, technical, or theological claims.
Pass condition
Record IDs, source records, verdict language, and generated exports make the claim inspectable instead of merely forceful.
Owner
Research proof
Proof the claim index

Gate 04

AI boundary

The AI Engine sounds like inquiry, not oracle, prophecy, priesthood, or command

Test
Review AI Engine prompts, helper copy, response notices, and any page that invites machine-assisted interpretation.
Pass condition
Machine output remains provisional, bounded, reviewable, and visibly subordinate to editorial judgment.
Owner
AI proof
Review AI governance

Gate 05

Intake and support handoff

Every form tells the truth about what happens next and how records move

Test
Submit or inspect Signals, Contact, Program Intake, Support, Privacy, and Terms copy before promotion.
Pass condition
Storage, admin export, response expectations, support fallback, and future external-tool migration are explicit enough for launch operations.
Owner
Operations proof
Proof privacy and export language

Gate 06

Publication readiness

First essays and archive cards carry track, record, and review context

Test
Read Journal, single-post cards, excerpt cards, release desk, and launch priorities with the first public essays in place.
Pass condition
The archive explains publication status honestly, avoids empty social proof, and routes serious claims into the right research or review context.
Owner
Publication proof
Proof the release desk

Gate 07

Governance and amendment trail

Policy, review notices, and canonical files agree with the launch state

Test
Compare Charter, Standards, Review Notices, Privacy, Terms, Community Guidelines, and the human Site Map.
Pass condition
Current policy language matches live forms, review notices identify material change, and canonical files are stable enough to cite.
Owner
Governance proof
Proof review notices

Archive Pipeline

How material enters and survives the archive

The journal remains the laboratory, verified dossiers earn a higher evidentiary banner, and canonical files move only under slower review.

Publication Desk

Journal protocols

  • Publication standard Public texts should remain calm, exact, literate, and proportionate. The journal is a record of thought, not a stage for empty provocation.
  • Archive status Once published, essays enter the public archive and are treated as part of the institution's ongoing record rather than disposable feed content.
  • Revision discipline Routine corrections may occur, but major doctrinal changes belong in canonical files or formal editorial updates rather than silent rewrites.
  • Path to canon Experimental work is tested in the journal first. Only mature, coherent material should advance into manifesto, charter, standards, or pillar essays.
Open the journal

Verification Threshold

Verified Research criteria

  • Claim proportionality A verified dossier states what kind of claim it is making: textual, historical, sociological, technological, or speculative.
  • Visible source trail Readers should be able to see where the argument comes from, why those sources matter, and where uncertainty remains.
  • Counter-reading awareness A serious dossier names competing interpretations instead of pretending disagreement only exists among the unserious.
  • Editorial review before banner use The Verified Research label is earned through review, revision, and evidentiary clarity, not granted as self-description.
Open verified research

AI Governance

Machine-assisted inquiry under editorial authority

AI may stress-test assumptions and compare frames, but it cannot inherit the voice of doctrine, prophecy, or final judgment.

System posture

The engine responds in a calm, benevolent, non-directive tone designed to pressure assumptions rather than reward certainty.

Output contract

Each response is structured around hidden assumptions, adversarial reframing, and reflective questions so the system remains interpretive rather than oracular.

Boundary condition

No output may encourage harm, coercion, persecution, or grandiose certainty. The Foundation critiques systems and ideas, not protected groups.

Editorial oversight

The engine operates under the same standards as the public record. It can assist inquiry, but it cannot become doctrine, prophet, or final authority.

Promotion Ladder

Promotion ladder

Not every sharp thought belongs in the canon. This is the route from exploratory pressure-testing to public archive work to formal record review.

Stage 01

Pressure-test the claim before it borrows institutional authority

Early material belongs in adversarial inquiry, cohort reading, or exploratory notes until the assumptions, evidence posture, and likely counter-readings are clearer.

Use bounded inquiry and slower group study before anything tries to speak in the tone of finished doctrine.

Open the AI Engine Route into the cohort lane

Stage 02

Publish it in the archive where it can be cited and challenged

The journal is the public laboratory for essays, transmissions, and dossiers that need real scrutiny before they can be treated as stable institutional files.

Publication creates archive status, not untouchability. The point is visible testing, not premature canonization.

Open the journal Read the doctrine Q&A

Stage 03

Earn higher trust through the verified-research threshold

A dossier receives the Verified Research banner only after review, visible sources, and enough counter-reading awareness to survive disagreement.

The banner is an earned evidentiary signal, not a branding flourish or self-issued credential.

Open verified research Enter the contributor lane

Stage 04

Promote only through visible governance and review

Material that proves durable may move into manifesto, charter, standards, or other canonical files, but only with explicit editorial review and a visible amendment trail where needed.

Canon should move more slowly than the archive so readers can trust that revision was intentional rather than smuggled in.

Open the review log Read the charter

Review Cadence

Review cadence and amendment pressure

Publication rhythm, quarterly coordination, and formal notice thresholds keep visible learning attached to institutional change.

Weekly Signals

Signals Briefing

Short-form releases orient readers to emerging patterns, fresh source finds, and archive movement without requiring a full dossier reading session.

Primary outward habit loop while the archive is still maturing.

Monthly File

Journal dossier or essay release

A steadier journal rhythm turns the institution from a declaration into an archive with visible continuity, sequence, and citation value.

Priority tracks: Verified Research, History of the Spirit, and Algorithmic Eschatology.

Quarterly Review

Directorate coordination cycle

Doctrine, research, and publication should review whether the atlas, archive, and briefing layer are still aligned before the next public push.

This is where the named directorates start behaving like operating offices.

Amendment Marker

First public record review

Once one full cycle of dossiers, briefings, and archive releases has been completed, the first formal amendment notice should be published as FFTAC-REC-01.

Phase-four legitimacy begins when the institution learns publicly and records the revision.

FFTAC-REC-00

Baseline

Launch baseline

Founding public edition registered as the baseline record

Registers the current launch-era public edition as the comparison point for future amendments, corrections, and promoted research changes.

Active baseline during prelaunch buildout.

Open notice

FFTAC-REC-01

Queued

Full-cycle review

First formal review after the initial atlas, briefing, and archive cycle

The first formal review will record what changed once the institution completes one outward cycle of atlas expansion, signals briefings, and durable journal releases.

Queued; the threshold has been named publicly but not yet satisfied.

Open notice