Skip to content
wiki.fftac.org

Wiki Wizard Alignment

**Site relevance:** Antichrist.net

**Memory type:** UAI memory file

**Source path:** Antichrist.net/.uai/wiki-wizard-alignment.uai

**Size:** 2.7 KB

Summary

UAIX And LLM Wiki Wizard Alignment

Source Headings

  • UAIX And LLM Wiki Wizard Alignment
  • Required Local Behavior
  • Wiki Routing
  • Talisman Tooling Ownership

Source Preview

This source file is short enough to preview directly on its source-memory page.

---
uai: "1.0"
type: wiki-wizard-alignment
project: "Antichrist.net"
created: "2026-06-13"
updated: "2026-06-13"
status: active
uaix_wizard_source: "https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-file-handoff-llm-wiki"
llmwikis_wizard_source: "https://llmwikis.org/tools/llm-wiki-setup-wizard/"
long_memory_destination: "https://wiki.fftac.org/antichrist/"
---

# UAIX And LLM Wiki Wizard Alignment

Use UAIX.org AI Memory Package Wizard guidance for local .uai package shape, File Handoff, Project Handoff, startup/read order, next-recursive prompt behavior, and generated package boundaries.

Use LLMWikis.org Setup Wizard guidance for LLM Wiki planning, fresh setup versus existing-system update, raw source preservation, reviewed wiki pages, index/log topology, metadata, trust labels, and site-scoped public memory structure.

## Required Local Behavior

- Keep active local AI memory in .uai/; do not create a separate default memory folder, scattered Markdown notes, or wiki folder inside the source tree as a substitute for .uai/.
- .uai folders use .uai for AI instruction/memory text, .human for human-operator explanation, and .json for structured data. Legacy evidence with other extensions should be retired or archived intentionally rather than copied forward as the active pattern.
- For code-bearing/project handoff scope, read or create coding standards, architecture, test-plan, and next-recursive prompt records before broad code edits.
- Suggested Next Prompt output must be visible to the human and include Feature/improvement focus, Code/source changes, and Automated tests/checks sections with real content or an explicit no-op/source-validation only stop condition.

## Wiki Routing

- Reviewed long memory for this project routes to https://wiki.fftac.org/antichrist/.
- In shared Wiki.FFTAC.org systems, each site gets its own namespace. Site-owned files, concepts, and reports live under that site namespace.
- Organization-wide files belong in /org/ or an explicit global/wiki/global area.
- Root /files/, /concepts/, and /reports/ pages are invalid if they flatten all sibling-site memory. If present, they must be crawl maps that list organization-level files and links to each individual site's index.

## Talisman Tooling Ownership

- UAIX.org owns official Talisman client/manager specs, docs, package behavior, validators, public setup guidance, and official WordPress, PHP, .NET, and Python client/manager development and distribution.
- Teleodynamic.com is the Talisman and philosophical fulcrum for this ecosystem; client receiver configuration points there unless the human names a bounded exception.
- Dogfood findings from this project can update UAIX tooling guidance and Teleodynamic theory/public guidance through reviewed source changes.
Website health report