Skip to content
wiki.fftac.org

Foundation Content - Source Excerpt 03

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

'eyebrow' => 'Charter',
            'title'   => 'Institutional Charter',
            'summary' => 'Defines institutional purpose, public authority, non-coercion boundaries, and the obligations under which the Foundation may speak in public.',
            'page'    => 'charter',
            'cta'     => 'Read the charter',
        ),
        array(
            'eyebrow' => 'Review Log',
            'title'   => 'Review Notices',
            'summary' => 'Keeps baseline registrations, queued amendments, and staged governance reviews visible so institutional change cannot hide inside quiet edits.',
            'page'    => 'review_notices',
            'cta'     => 'Open the review log',
        ),
        array(
            'eyebrow' => 'Research',
            'title'   => 'Research Program',
            'summary' => 'Organizes the research atlas, claim index, timelines, and comparative dossiers across dogma, power, sacred texts, symbolism, and technology.',
            'page'    => 'research',
            'cta'     => 'View research directives',
        ),
        array(
            'eyebrow' => 'Recovery',
            'title'   => 'Recovery Guide',
            'summary' => 'Offers a structured destination for readers leaving prophecy panic, fear-based religion, and obedience systems that colonized conscience.',
            'page'    => 'recovery',
            'cta'     => 'Open the recovery guide',
        ),
        array(
            'eyebrow' => 'Doctrine Q&A',
            'title'   => 'Doctrine Q&A',
            'summary' => 'Collects the threshold questions readers, journalists, skeptics, and recovery readers ask before trusting the rest of the archive.',
            'page'    => 'questions',
            'cta'     => 'Review the question file',
        ),
        array(
            'eyebrow' => 'Standards',
            'title'   => 'Editorial Standards',
            'summary' => 'Specifies interpretive rules, evidence posture, AI constraints, and publication discipline for public-facing work.',
            'page'    => 'standards',
            'cta'     => 'Review the standards',
        ),
        array(
            'eyebrow' => 'About',
            'title'   => 'About The Foundation',
            'summary' => 'Explains the institutional markers, named offices, core records, research lenses, and current priorities behind the public archive.',
            'page'    => 'about',
            'cta'     => 'Read the institutional brief',
        ),
        array(
            'eyebrow' => 'Support',
            'title'   => 'Support the Record',
            'summary' => 'Shows how launch-time contributions sustain hosting, research files, publication rhythm, and the public infrastructure behind the archive.',
            'page'    => 'support',
            'cta'     => 'Open the support brief',
        ),
    );
}

/**
 * Shared copy for the review-notice interface.
 *
 * @return array<string, string>
 */
function antichrist_engine_foundation_review_notice_interface_copy()
{
    return array(
        'hero_lead'        => 'A governed log for baseline registrations, queued amendments, and staged review thresholds across the public record.',
        'hero_summary'     => 'This page exists so canonical change can be named, scoped, and challenged in public rather than drifting through quiet edits or implied authority.',
        'panel_subline'    => 'No silent drift. No hidden canon. No theatrical amendment theater.',
        'register_title'   => 'Notice register',
        'register_summary' => 'Each notice names the trigger, affected record scope, and next action required before the public file changes in a material way.',
        'protocol_title'   => 'Review discipline',
        'protocol_summary' => 'These rules keep the log legible enough for researchers, skeptics, and future contributors to audit how the institution changes.',
        'impact_title'     => 'Affected public records',
        'impact_summary'   => 'Canonical files, atlas routes, and publication layers already named inside the review queue so later amendments can cite precise targets instead of vague institutional mood.',
        'route_label'      => 'Machine route',
    );
}

/**
 * Status labels for formal review notices.
 *
 * @return array<string, array<string, string>>
 */
function antichrist_engine_foundation_review_notice_statuses()
{
    return array(
        'baseline' => array(
            'label'   => 'Baseline',
            'summary' => 'The reference state against which future formal changes should be measured.',
        ),
        'queued' => array(
            'label'   => 'Queued',
            'summary' => 'A named formal review is expected but not yet issued.',
        ),
        'staged' => array(
            'label'   => 'Staged',
            'summary' => 'A governance review is anticipated if the related surface expands or hardens.',
        ),
    );
}

/**
 * Review-notice protocols for public governance discipline.
 *
 * @return array<int, array<string, string>>
 */
function antichrist_engine_foundation_review_notice_protocols()
{
    return array(
        array(
            'title'   => 'No silent drift',
            'summary' => 'Material shifts in doctrine, standards, atlas posture, or institutional boundaries should be named in the log instead of being smuggled through quiet rewrites.',
        ),
        array(
            'title'   => 'Name the affected records',
            'summary' => 'Each notice should point back to the exact public files, record IDs, or routes that would be touched if the review matures into a formal change.',
        ),
        array(
            'title'   => 'Keep corrections proportional',
            'summary' => 'Typos and housekeeping can be corrected routinely, but anything that changes public meaning, authority, or boundary-setting belongs in the notice system.',
        ),
        array(
            'title'   => 'Leave a machine-readable trail',
            'summary' => 'The review log should remain linkable, searchable, and exportable enough that outside researchers can follow the governance trail without reverse-engineering screenshots or rumors.',
        ),
    );
}

/**
 * Review-notice entries used by the governance log.
 *
 * @return array<int, array<string, mixed>>
 */
function antichrist_engine_foundation_review_notice_entries()
{
    return array(
        array(
            'record_id'        => 'FFTAC-REC-00',
            'status'           => 'baseline',
            'phase'            => 'Launch baseline',
            'title'            => 'Founding public edition registered as the baseline record',
            'summary'          => 'Registers the current launch-era public edition as the comparison point for future amendments, corrections, and promoted research changes.',
            'scope'            => 'Manifesto, charter, standards, research atlas, recovery routes, journal shell, and launch discovery infrastructure.',
            'trigger'          => 'Initial governed public release of the Foundation record.',
            'current_state'    => 'Active baseline during prelaunch buildout.',
            'next_action'      => 'Use this baseline whenever a later notice needs to describe what changed and why.',
            'affected_records' => array('FFTAC-MAN-01', 'FFTAC-CHR-01', 'FFTAC-STD-01', 'FFTAC-RSR-01', 'FFTAC-RCV-01', 'FFTAC-JRN-01', 'FFTAC-SMP-01'),
            'affected_pages'   => array('manifesto', 'charter', 'standards', 'research', 'recovery', 'journal', 'sitemap'),
            'route_target'     => 'charter',
            'route_cta'        => 'Inspect the charter',
        ),
        array(
            'record_id'        => 'FFTAC-REC-01',
            'status'           => 'queued',
            'phase'            => 'Full-cycle review',
            'title'            => 'First formal review after the initial atlas, briefing, and archive cycle',
            'summary'          => 'The first formal review will record what changed once the institution completes one outward cycle of atlas expansion, signals briefings, and durable journal releases.',
            'scope'            => 'Canonical doctrine, publication promotion rules, and the threshold for moving mature research into the official record.',
            'trigger'          => 'Completion of the first full cycle named in the charter.',
            'current_state'    => 'Queued; the threshold has been named publicly but not yet satisfied.',
            'next_action'      => 'Issue a notice that cites the baseline, names affected files, and explains each adopted revision in plain language.',
            'affected_records' => array('FFTAC-MAN-01', 'FFTAC-CHR-01', 'FFTAC-STD-01', 'FFTAC-JRN-01'),