Foundation Content - Source Excerpt 42

Back to Foundation Content

Summary

This source excerpt preserves a bounded section of Anti-Christ.org/wp-content/plugins/fftac-foundation-core/inc/foundation-content.php so readers can inspect the evidence without opening the full source file.

**Source path:** Anti-Christ.org/wp-content/plugins/fftac-foundation-core/inc/foundation-content.php

</ul>

<h2>Methods</h2>
<p>The Foundation works through long-form essays, comparative interpretation, archival reading, structured dossiers, visible source trails, transparent moral questions, and carefully bounded AI-assisted reframing. We treat biblical criticism, church history, sociology of power, recovery knowledge, and technology studies as complementary lenses rather than rival tribes.</p>

<h2>Publication Path</h2>
<p>Research begins in the pillars, expands through the atlas, claim dossiers, texts, and signals briefings, and is tested publicly through the Journal and Ask the Adversary. Canonical documents remain the frame; active publications remain the laboratory. Material that proves durable may be promoted into the official record through editorial review.</p>
HTML;
}

/**
 * Default content for the standards page.
 *
 * @return string
 */
function antichrist_engine_foundation_standards_content()
{
    return <<<'HTML'
<p class="foundation-lead">The Foundation publishes under standards designed to preserve seriousness, interpretive integrity, and institutional discipline.</p>

<h2>Tone and Register</h2>
<p>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.</p>

<h2>Public Voice Test</h2>
<p>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.</p>

<h2>Launch Readiness Rule</h2>
<p>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.</p>

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

<h2>Moral Method</h2>
<p>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.</p>

<h2>Evidence Posture</h2>
<p>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.</p>

<h2>AI Governance</h2>
<p>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.</p>

<h2>Promotion Rule</h2>
<p>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.</p>
HTML;
}

/**
 * Shared copy for the editorial-standards surface.
 *
 * @return array<string, string>
 */
function antichrist_engine_foundation_standards_interface_copy()
{
    return array(
        'hero_lead'        => 'The standards file turns tone, evidence, machine use, publication, and amendment discipline into a visible operating surface before the archive goes fully public.',
        'panel_subline'    => 'Calm register. Visible sources. Bounded machine use. Promotion by review instead of drift.',
        'map_title'        => 'The standards map',
        'map_summary'      => '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_title'    => 'Institutional posture before publication',
        'posture_summary'  => 'These assurances keep the Foundation from reenacting the panic, coercion, and theatrical certainty it critiques elsewhere.',
        'voice_title'      => 'Launch voice checks',
        'voice_summary'    => 'Every prominent public page should pass these checks before promotion, outreach, or citation pressure makes the first impression harder to revise.',
        'proof_title'      => 'Final proof gates before promotion',
        'proof_summary'    => 'These gates turn the launch voice standard into concrete page, route, and handoff checks so final proofing can happen without guessing what readiness means.',
        'archive_title'    => 'How material enters and survives the archive',
        'archive_summary'  => 'The journal remains the laboratory, verified dossiers earn a higher evidentiary banner, and canonical files move only under slower review.',
        'ai_title'         => 'Machine-assisted inquiry under editorial authority',
        'ai_summary'       => 'AI may stress-test assumptions and compare frames, but it cannot inherit the voice of doctrine, prophecy, or final judgment.',
        'promotion_title'  => 'Promotion ladder',
        'promotion_summary'=> 'Not every sharp thought belongs in the canon. This is the route from exploratory pressure-testing to public archive work to formal record review.',
        'review_title'     => 'Review cadence and amendment pressure',
        'review_summary'   => 'Publication rhythm, quarterly coordination, and formal notice thresholds keep visible learning attached to institutional change.',
    );
}

/**
 * Route map for the editorial-standards surface.
 *
 * @return array<int, array<string, string>>
 */
function antichrist_engine_foundation_standards_route_map()
{
    return array(
        array(
            'eyebrow' => 'Posture',
            'title'   => 'Start with the non-negotiable assurances',
            'summary' => 'Read the rules that keep participation voluntary, critique institutional, AI bounded, and canonical files stable enough to cite.',
            'anchor'  => 'institutional-posture',
            'cta'     => 'Open the posture layer',
        ),
        array(
            'eyebrow' => 'Voice',
            'title'   => 'Run the prelaunch public-voice check',
            'summary' => 'Make sure the site explains the domain, moral center, recovery posture, AI boundary, support ask, and contributor invitation before critique becomes noisy.',
            'anchor'  => 'launch-voice-checks',
            'cta'     => 'Open voice checks',
        ),
        array(
            'eyebrow' => 'Proof',
            'title'   => 'Use the final proof gates before promotion',
            'summary' => 'Convert launch voice standards into concrete checks for first-contact copy, recovery safety, evidence posture, intake handoff, and publication readiness.',
            'anchor'  => 'launch-proof-gates',
            'cta'     => 'Open proof gates',
        ),
        array(
            'eyebrow' => 'Archive',
            'title'   => 'See how publication and verification interact',
            'summary' => 'Track the difference between ordinary archive release, verified research review, and the slower movement into canonical status.',
            'anchor'  => 'archive-pipeline',
            'cta'     => 'Inspect the archive pipeline',
        ),
        array(
            'eyebrow' => 'Machine',
            'title'   => 'Review the AI governance contract',
            'summary' => 'The AI Engine can help pressure assumptions, but it stays under the same editorial discipline as every other public surface.',
            'anchor'  => 'ai-governance',
            'cta'     => 'Review AI boundaries',
        ),
        array(
            'eyebrow' => 'Promotion',
            'title'   => 'Follow the path from draft to canon',
            'summary' => 'Ideas should move through testing, publication, verification, and review rather than being promoted by excitement alone.',
            'anchor'  => 'promotion-ladder',
            'cta'     => 'Trace the promotion ladder',
        ),
        array(
            'eyebrow' => 'Review',