Foundation Content - Source Excerpt 51

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

'note'             => 'Best for profile listings, directory entries, deck builders, social editors, and anyone reusing marks under deadline.',
            'includes'         => array(
                'Site-link guide for naming and destination discipline.',
                'Press-kit bundle for posters, wallpapers, and canonical public files.',
                'Seal pack for vector and square-icon reuse.',
                'Visual studies and symbol rules for context without improvisation.',
            ),
            'primary_target'   => 'downloads',
            'primary_anchor'   => 'site-link-guide',
            'primary_cta'      => 'Open the link guide',
            'secondary_target' => 'downloads',
            'secondary_anchor' => 'seal-pack',
            'secondary_cta'    => 'Open the seal pack',
            'keywords'         => 'identity packet naming packet visual identity packet site link guide seal pack directory listing',
        ),
        array(
            'eyebrow'          => 'Research Packet',
            'title'            => 'Research reuse packet',
            'summary'          => 'This packet is for fact-checkers, prototype builders, and serious readers who need source-aware flat files instead of screenshots or manual copy-paste.',
            'note'             => 'Best when the audience needs claims tables, chronology, provenance, or machine-readable research routes fast.',
            'includes'         => array(
                'Claims, timeline, projection, and source CSV exports.',
                'Unified NDJSON record stream for ingestion workflows.',
                'Provenance note for generation time, route lineage, and attribution.',
                'Atlas export desk and source-library routes for proof behind the files.',
            ),
            'primary_target'   => 'downloads',
            'primary_anchor'   => 'research-data-exports',
            'primary_cta'      => 'Open research exports',
            'secondary_target' => 'research',
            'secondary_anchor' => 'export-desk',
            'secondary_cta'    => 'Open the export desk',
            'keywords'         => 'research reuse packet data packet claim tables csv ndjson provenance export desk briefing packet',
        ),
    );
}

/**
 * Default content for the privacy policy page.
 *
 * @return string
 */
function antichrist_engine_foundation_privacy_content()
{
    return <<<'HTML'
<p class="foundation-lead">This notice explains what the Foundation stores when readers use public forms, optional membership, the AI Engine, analytics event hooks, and protected collaboration spaces.</p>

<h2>What We Collect</h2>
<ul>
    <li>Signals Briefing signups may store a name, email address, and optional reading interest.</li>
    <li>Contact Desk messages may store a name, email address, route, context, subject, and message body so the inquiry can be routed.</li>
    <li>Program intake submissions may store a name, email address, selected lane, role, and intake notes.</li>
    <li>Membership accounts may store the profile data needed to authenticate users and support protected participation.</li>
    <li>AI Engine requests may include the prompt a signed-in reader submits, recent browser-local conversation context, encrypted personal API key metadata, and the model response returned to the browser.</li>
    <li>Security controls may store timestamps, rate-limit fingerprints, and operational logs needed to reduce spam, flooding, or malicious automation.</li>
</ul>

<h2>Why We Collect It</h2>
<p>The Foundation uses this information to review submissions, respond to inquiries, operate protected member access, return bounded AI responses, and defend public forms against abuse. Data collection here is functional and editorial, not behavioral advertising.</p>

<h2>AI Engine Requests</h2>
<p>When the AI Engine is configured, a submitted prompt and recent browser-local conversation context may be sent to the selected model provider so a response can be generated. The response is treated as an inquiry aid, not a canonical public record, professional advice, or machine authority. Readers should avoid submitting secrets, credentials, or private third-party information into the prompt field. Personal API keys, if saved, are stored encrypted in the user's WordPress profile and are never displayed back after saving.</p>

<h2>Analytics Event Hooks</h2>
<p>The theme dispatches provider-neutral browser events for actions such as navigator use, search, downloads, support clicks, research filters, public form submissions, and AI prompt submission. These events are designed to support future privacy-aware measurement without placing an analytics provider in the templates by default. If a third-party analytics provider is connected later, this notice should be reviewed before public promotion.</p>

<h2>Admin Exports</h2>
<p>Administrators can export private Signals, Contact Desk, Program Intake, and combined launch-intake records as CSV from the internal launch readiness page. Those exports are operational handoffs for future newsletter, support, CRM, or program tooling. They are not public downloads and should be handled as private working files.</p>

<h2>Cookies and Technical Storage</h2>
<p>WordPress may set functional cookies for login, session continuity, or interface preferences when protected access is used. Public forms also rely on server-side anti-automation checks. If future analytics, consent tooling, or external mailing systems are added, this notice should be revised before those systems go live.</p>

<h2>What We Do Not Offer</h2>
<ul>
    <li>No promise that belief, deconstruction, or reading history will be sold as an audience segment.</li>
    <li>No promise that every submission becomes a relationship, membership, or publication.</li>
    <li>No automatic approval path from a form submission into the institution's protected spaces.</li>
</ul>

<h2>Retention and Review</h2>
<p>Stored submissions, account records, encrypted AI key metadata, operational logs, and private exports may be retained for editorial continuity, security review, migration, and protected collaboration until they are no longer operationally useful. Browser-local AI conversation history can be cleared from the AI console and should not be treated as a permanent Foundation record. The Foundation should keep stored personal data proportional to the seriousness of the relationship and delete what no longer needs to be preserved.</p>
HTML;
}

/**
 * Default content for the terms of use page.
 *
 * @return string
 */
function antichrist_engine_foundation_terms_content()
{
    return <<<'HTML'
<p class="foundation-lead">This site is a public philosophy and research archive. It exists for study, critique, publication, and disciplined inquiry rather than worship, panic, or coercive recruitment.</p>

<h2>Use Of The Site</h2>
<p>You may read, cite, and share public materials from this site so long as you do not misrepresent the Foundation's position, impersonate its editors, or use the platform to facilitate harassment, fraud, or illegal activity.</p>

<h2>Educational Purpose</h2>
<p>The Foundation publishes educational, interpretive, and editorial material. Nothing here should be treated as legal, medical, financial, or pastoral advice. The site exists to sharpen judgment, not to replace it.</p>

<h2>AI Engine Use</h2>
<p>The AI Engine is a bounded inquiry surface. Its responses may help pressure assumptions, generate questions, or route a reader toward slower research, but they are not final authority, professional advice, doctrine, or permission to outsource conscience. AI-assisted submissions remain subject to the same editorial standards as any other contribution.</p>

<h2>Downloads, API Use, and Attribution</h2>
<ul>
    <li>Public downloads and research endpoints may be referenced, quoted, or incorporated into analysis with attribution back to <strong>anti-christ.org</strong>.</li>
    <li>Use of public materials does not create endorsement, partnership, membership, or speaking authority on behalf of the Foundation.</li>
    <li>Abusive scraping, automated disruption, or attempts to degrade the public site are outside permitted use.</li>
</ul>

<h2>Editorial Boundary</h2>
<p>The Foundation may revise, remove, reorganize, or expand public material as the record matures. Publication remains governed, not crowd-owned, and protected spaces may be opened or closed according to operational and editorial judgment.</p>

<h2>User Submissions</h2>
<p>Messages, applications, contributor notes, AI-assisted drafts, and future public comments are subject to review. Submission does not guarantee reply, publication, approval, or continued access. Material that violates the Foundation's published standards or conduct rules may be refused or removed.</p>