AI Content - Source Excerpt 04

Back to AI Content

Summary

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

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

'eyebrow' => 'Human Route',
            'title'   => 'Contact the desk for routed follow-up',
            'summary' => 'If the issue is a correction, media request, sensitive recovery question, or launch-critical problem, leave the prompt surface and use a human-reviewed route.',
            'note'    => 'Use this when the matter needs context, deadlines, accountability, or editorial review.',
            'target'  => 'contact',
            'args'    => array('route' => 'general-editorial'),
            'anchor'  => 'contact-desk',
            'cta'     => 'Open the contact desk',
        ),
    );
}

/**
 * Shared copy for the AI engine interface shell.
 *
 * @return array<string, string>
 */
function antichrist_engine_foundation_ai_interface_copy()
{
    return array(
        'hero_lead'          => 'Ask the Adversary is now a signed-in AI console for live, conversation-aware reframing under Foundation standards.',
        'status_live'        => 'Short live responses can use the limited Foundation key. Larger conversations require your own OpenAI API key.',
        'status_waiting'     => 'Live responses require either a saved personal OpenAI API key or a configured Foundation key.',
        'map_title'          => 'Inquiry command map',
        'map_summary'        => 'Start here if you want to use the AI Engine deliberately: choose the right prompt lane, understand what a governed answer should do, follow the flagship systems questions, and leave the prompt window when the issue needs archive depth or human review.',
        'protocol_title'     => 'How the inquiry engine is governed',
        'prompt_title'       => 'Prompt lanes for different kinds of pressure',
        'prompt_summary'     => 'Not every question should be phrased the same way. These lanes help readers arrive with better prompts and clearer expectations.',
        'contract_title'     => 'What a good response should actually contain',
        'contract_summary'   => 'The engine is useful only if it exposes assumptions, reframes the problem, and returns agency to the reader instead of performing certainty.',
        'frontier_title'     => 'Flagship systems frontier',
        'frontier_summary'   => 'The AI Engine is strongest when it points directly at the live institutional question: how antichrist language migrates into machine authority, biometric governance, and digital obedience systems.',
        'next_title'         => 'Where inquiry should go next',
        'next_summary'       => 'The engine is a threshold layer, not the whole institution. These routes turn a useful answer into research, publication, recovery, or human follow-up.',
        'form_label'         => 'Question, doctrine, or belief under review',
        'placeholder'        => 'Example: Why does obedience feel moral even when the command was inherited rather than earned?',
        'submit'             => 'Send to the Engine',
        'hint'               => 'Conversation history stays in this browser. Outputs are philosophical prompts, not authority, advice, or doctrine.',
        'console_title'      => 'Ask the Adversary',
        'console_summary'    => 'Choose a response flavor, keep the exchange focused, and use the transcript like any modern AI chat without letting the machine outrank your judgment.',
        'flavor_title'       => 'Personality flavor deck',
        'flavor_summary'     => 'Each flavor changes the private response posture, the expected output shape, and the safest next step without exposing hidden system instructions.',
        'protocol_deck_title'=> 'Inquiry protocol deck',
        'protocol_deck_summary'=> 'Protocols make the engine perform a specific operation: audit authority, decode fear, map systems, build evidence, forge a public note, or drill the counterclaim.',
        'session_title'      => 'Session Tools',
        'session_heading'    => 'Keep your local transcript portable',
        'session_summary'    => 'Watch prompt and context pressure, then copy, export, or restore the browser transcript without turning private chat history into a server-side archive.',
        'workspace_title'    => 'Workspace Brief',
        'workspace_heading'  => 'Anchor the next inquiry without changing the server archive',
        'workspace_summary'  => 'Save a short local note for the claim, draft, source trail, or recovery context you are working with. Add it to the prompt only when you want the model to see it.',
        'workspace_label'    => 'Local working brief',
        'workspace_placeholder'=> 'Example: I am drafting a short note on biometric access control and inherited mark-of-the-beast fear. Keep the answer structural, calm, and citation-aware.',
        'workspace_policy'   => 'The brief stays in this browser until you add it to the prompt, export it, or save it inside a local snapshot.',
        'session_vault_title'=> 'Local session vault',
        'session_name_placeholder'=> 'Name this local snapshot',
        'session_saved_empty'=> 'No saved snapshots yet',
        'session_policy'     => 'Imports replace the transcript stored in this browser only. Review sensitive material before exporting or sharing.',
        'share_title'        => 'Share an AI output',
        'share_summary'      => 'Choose an assistant response, give it a title, and turn it into a private draft, a journal review item, or a public post under your member profile.',
        'share_policy'       => 'Shared outputs are AI-assisted user posts. They do not become Foundation doctrine unless separately reviewed and published as official record.',
        'gate_title'         => 'Sign in to use the AI Engine',
        'gate_summary'       => 'The live form is gated so model access, personal keys, and abuse controls stay tied to an account instead of a public anonymous endpoint.',
        'key_title'          => 'Personal API key',
        'key_summary'        => 'The Foundation key is limited to short prompts so public launch costs stay controlled. Save your own OpenAI API key for larger token use, deeper history, or longer responses.',
        'key_instructions'   => 'Create an API key in your OpenAI account, paste it here, and save it. The theme encrypts it in your user profile, never displays it back, and lets you remove it at any time.',
        'site_key_policy'    => 'Foundation key: short prompts only, low output cap, strict rate limit.',
        'user_key_policy'    => 'Your key: longer prompts and conversation history, still bounded by abuse controls.',
        'empty_chat'         => 'Choose a flavor or starter prompt, then send the first question. The hidden flavor prompt is applied server-side and never shown in the transcript.',
        'share_empty'        => 'Send a prompt or choose Share on an assistant answer to prepare a post.',
    );
}

/**
 * Default content for the AI engine page.
 *
 * @return string
 */
function antichrist_engine_foundation_ai_content()
{
    return <<<'HTML'
<p class="foundation-lead">Ask the Adversary is not a prophecy machine. It is a philosophical reframing engine built to expose hidden assumptions, inherited structures, counterfeit authority, and unquestioned premises.</p>

<p>Ask the Adversary is a bounded inquiry interface governed by the Foundation's charter and standards. It does not announce revelation, issue commands, or replace editorial judgment.</p>

<h2>Why It Exists</h2>
<p>Machine-assisted inquiry is useful only when it returns agency to the reader. The engine should make assumptions visible, separate panic from structure, and help people ask better questions without turning the machine into a priest, judge, oracle, or obedience rail.</p>

<h2>What The Engine Is For</h2>
<ul>
    <li>Expose hidden assumptions inside beliefs, fears, and moral reflexes.</li>
    <li>Reframe inherited doctrines under adversarial pressure.</li>
    <li>Translate prophecy panic into systems questions about authority, access, visibility, and control.</li>
    <li>Generate better questions for research, writing, and self-examination.</li>
    <li>Help users separate institutional language from personal conviction.</li>
</ul>

<h2>How To Use It Well</h2>
<ul>
    <li>Bring one belief, panic script, or moral reflex at a time instead of asking for a synthetic worldview.</li>
    <li>Name the fear, doctrine, technology, or authority structure you want pressured.</li>
    <li>Treat the answer as a route into slower judgment, not a machine verdict that ends the matter.</li>
    <li>Leave the engine when the question needs sources, chronology, recovery care, or human review.</li>
</ul>

<h2>Operating Boundary</h2>
<p>The engine remains interpretive, non-directive, and benevolent. Its responses are prompts for thought, not decisions for life. If an answer cannot survive scrutiny, it has no claim to authority.</p>