11 User AI Architecture - Source Excerpt 03 - Testing

Summary

This source excerpt begins near Testing and preserves the surrounding evidence from Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/11-user-ai-architecture.md.

**Source path:** Wiki.FFTAC.org/raw/system-archives/anti-christ.org/docs-archive/2026-05-10/docs/11-user-ai-architecture.md

- document a human support path for users who paste sensitive recovery material into local transcripts and then ask for help outside the AI console

## Testing

After AI changes, run:

' ' ' powershell
php -l .\wp-content\plugins\fftac-ai-engine\inc\ai-engine.php
php -l .\wp-content\plugins\fftac-ai-engine\inc\ai-content.php
php -l .\wp-content\themes\antichrist-engine\template-ai-engine.php
npm.cmd run build:assets
npm.cmd run check:assets
php tests/run.php
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\test-theme.ps1
' ' ' 

For release packages, run:

' ' ' powershell
powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\build-deploy-zips.ps1
' ' ' 

## Edit Rules

- Do not restore anonymous AI prompt submission.
- Do not store plaintext personal API keys.
- Do not put hidden persona or protocol prompts into template markup or localized JavaScript.
- Keep admin-edited persona system prompts in `Settings -> FFTAC AI Engine`; they are stored in options and applied server-side only.
- Do not persist chat transcripts in WordPress except when a signed-in user explicitly shares a selected AI output into the post layer.
- Do not silently send the workspace brief to the server. It must remain local until the user deliberately adds it to the visible prompt text.
- Do not make transcript import/export a server upload path unless retention, moderation, deletion, and privacy policy implications are reviewed first.
- Do not turn local snapshots into server-side saved sessions unless retention, deletion, account export, moderation, and privacy policy implications are reviewed first.
- Do not raise Foundation-key limits without a cost and abuse review.
- Keep docs current when key policy, personas, protocols, page orientation surfaces, workspace brief behavior, session tools, share behavior, AJAX endpoints, or AI analytics events change.