Foundation Content - Source Excerpt 37
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
'summary' => 'The charter makes visible review part of the institution itself so public learning can occur without pretending the founding draft was flawless.',
'cards' => array(
array(
'eyebrow' => 'Visible Review',
'title' => 'Material change belongs in the review log',
'summary' => 'Canonical shifts should produce named notices, defined scope, and visible next actions instead of being smuggled through quiet rewrites.',
'target' => 'review_notices',
'anchor' => 'notice-register',
'cta' => 'Open the notice register',
),
array(
'eyebrow' => 'FFTAC-REC-01',
'title' => 'The first formal marker remains part of the launch contract',
'summary' => 'The named threshold proves the institution intends to learn publicly once the first full cycle of research, publication, and governance has matured.',
'note' => 'The charter names this marker before the cycle arrives so amendment cannot later appear as an improvisation.',
'target' => 'review_notices',
'cta' => 'Inspect the queued marker',
),
array(
'eyebrow' => 'Promotion Rule',
'title' => 'Ideas move upward by review, not excitement',
'summary' => 'Exploratory insights should earn their way through publication, verification, and slower canonical review before they speak with institutional permanence.',
'target' => 'standards',
'anchor' => 'promotion-ladder',
'cta' => 'Trace the promotion ladder',
),
),
),
),
'privacy' => array(
array(
'anchor' => 'data-intake',
'eyebrow' => 'Data Intake',
'title' => 'What enters the system',
'summary' => 'The privacy file separates signups, routed forms, protected access, and abuse controls so readers can see exactly why information is being kept.',
'cards' => array(
array(
'eyebrow' => 'Signals',
'title' => 'Briefing signup data stays narrow',
'summary' => 'Signals subscriptions may keep a name, email address, and reading interest so editorial follow-up can remain relevant without becoming audience profiling.',
),
array(
'eyebrow' => 'Intake',
'title' => 'Program and contact forms collect operational context',
'summary' => 'Applications and routed messages may keep identity, role, route choice, and notes because editorial review needs enough information to answer proportionally.',
'target' => 'join',
'anchor' => 'program-intake',
'cta' => 'Open program intake',
),
array(
'eyebrow' => 'Access',
'title' => 'Protected participation needs account data',
'summary' => 'Member authentication only stores the profile information needed to maintain access, continuity, and accountable protected exchange.',
'target' => 'membership_portal',
'cta' => 'Open the membership portal',
),
array(
'eyebrow' => 'Participant Mirror',
'title' => 'Roster data stays secondary to WordPress identity',
'summary' => 'When Participants Database is active, member profiles and private intake may be mirrored into operational roster fields. WordPress users and Foundation private records remain the canonical audit trail.',
'target' => 'membership_portal',
'cta' => 'Review member profile tools',
),
array(
'eyebrow' => 'AI Engine',
'title' => 'AI requests may include prompts, local history, and key metadata',
'summary' => 'The signed-in AI Engine can send the current prompt and recent browser-local conversation context to the selected model provider. Personal keys are stored encrypted in user meta and are never displayed back after saving.',
'target' => 'ai_engine',
'cta' => 'Open the AI Engine',
),
),
),
array(
'anchor' => 'use-and-storage',
'eyebrow' => 'Use And Storage',
'title' => 'Why the Foundation keeps data at all',
'summary' => 'Collection is supposed to support routing, moderation, authentication, and abuse prevention rather than decorative engagement metrics or behavioral advertising.',
'cards' => array(
array(
'eyebrow' => 'Editorial Routing',
'title' => 'Messages are kept so they can be answered or reviewed',
'summary' => 'The Foundation stores submissions to route corrections, media requests, recovery inquiries, and applications into the right working lane.',
'target' => 'contact',
'anchor' => 'contact-desk',
'cta' => 'Open the contact desk',
),
array(
'eyebrow' => 'Protected Access',
'title' => 'Authentication supports accountable protected exchange',
'summary' => 'Account data exists to maintain continuity and security in protected spaces, not to build a hidden surveillance profile of participation.',
'target' => 'community',
'cta' => 'Review conduct boundaries',
),
array(
'eyebrow' => 'Anti-Abuse',
'title' => 'Security logs defend the site against noise and flooding',
'summary' => 'Timestamps, rate-limit fingerprints, and operational logs may be retained when they are necessary to reduce spam, scraping abuse, or malicious automation.',
),
),
),
array(
'anchor' => 'cookies-and-technical-storage',
'eyebrow' => 'Cookies And Technical Storage',
'title' => 'How browser and server-side persistence should behave',
'summary' => 'Technical storage should stay functional, proportionate, and revisable before outside analytics, mailing tools, or consent systems appear.',
'cards' => array(
array(
'eyebrow' => 'Functional Cookies',
'title' => 'Login and session continuity come first',
'summary' => 'WordPress may set the cookies needed for login state, session continuity, and basic interface preferences when protected access is in use.',
),
array(
'eyebrow' => 'Server Checks',
'title' => 'Anti-automation controls do not need spectacle',
'summary' => 'Public forms rely on server-side timing, honeypot, and rate-limit checks so the site can remain usable without turning readers into adtech inventory.',
),
array(
'eyebrow' => 'Future Tooling',
'title' => 'New third-party systems trigger notice revision',
'summary' => 'If analytics, consent tooling, or external mailing systems are added, this file should change before those systems go live.',
'target' => 'review_notices',
'cta' => 'Open review notices',
),
),
),
array(
'anchor' => 'retention-and-review',
'eyebrow' => 'Retention And Review',
'title' => 'How stored data stays proportionate',