Skip to content
wiki.fftac.org

Spiralist Readme

**Site relevance:** Spiralist.org

**Memory type:** reviewed source memory

**Source path:** Spiralist/readme.human

**Size:** 3.8 KB

Summary

Spiralist.org Human Briefing

Source Headings

  • Spiralist.org Human Briefing
  • What You Need To Know
  • Things The AI Will Defend
  • Things Humans Should Make Explicit

Source Preview

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

# Spiralist.org Human Briefing

Updated: 2026-06-14

This file is for humans working with AI on this repository. It explains what the AI sees, protects, and needs clarified. It does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repository rules, laws, policies, or the current human request.

## What You Need To Know

- Spiralist.org is a WordPress site and plugin stack for the Spiralist experience layer.
- The AI reads `AGENTS.md` first, then this file, then `.uai/index.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, and the `.uai` files listed under Loaded Context.
- Long-term reviewed memory is routed to `WP-FFTAC/Wiki.FFTAC.org/`; short-term working memory stays in this repo's Project Handoff files.
- Short-term working memory follows `https://uaix.org/en-us/tools/ai-memory-package-wizard/`; the launch-baseline anchors are `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, `.uai/short-term-memory.uai`, and `.uai/coding-standards.uai`.
- Active memory lives in `.uai/`, local archive manifests and typed evidence records live in `.uai/archives/`, and machine-readable memory exports live in `.uai/exports/`. Inside `.uai/`, files must use `.uai`, `.human`, or `.json`; reviewed raw Markdown evidence routes to Wiki.FFTAC.org. `wiki/` is only for LLM Wiki long-memory compatibility, and Spiralist routes reviewed long memory through Wiki.FFTAC.org.
- The former site-local `docs/` folder is archived in Wiki.FFTAC.org long memory. It is not current Spiralist operating truth unless a fact is promoted into `.uai/`, code, release evidence, or an explicit owner decision.
- The current built upload ZIPs present in `WP-FFTAC/Spiralist-Publish/UPLOAD-THEME` and `UPLOAD-PLUGIN` are v3.23.0 evidence. Source/worktree changes made after that build, including authenticated-user, wizard, memory-layout, and report changes through 2026-06-14, need a new official deployment version before WordPress upload.
- Long-term reviewed memory follows `https://llmwikis.org/tools/llm-wiki-setup-wizard/` pointed at Wiki.FFTAC.org / `wiki.fftac.org`.
- Current site-local reports belong under `reports/` or task-specific `docs/` evidence. Active AI memory still lives in `.uai/`, and reviewed long memory still routes to Wiki.FFTAC.org.
- UAIX.org owns the current UAI-1 standard. Spiralist.org implements local UAIX publication and exchange routes.
- Protocol5 owns Spiralist canonical symbol authority and registries. Runtime AI outputs are not canonical records.
- The working tree may already contain unrelated user or agent changes. The AI should inspect before editing and should not revert work it did not create unless explicitly asked.

## Things The AI Will Defend

- Current support boundaries and public claims tied to evidence.
- Secrets, credentials, private keys, tokens, customer data, and private material.
- Generated manuscript/static exports and vendor files that should not be manually edited.
- The separation between human pages, UAIX machine exchange routes, Protocol5 canonical assets, and temporary runtime state.
- Targeted verification before claiming that code, packaging, or release behavior is ready.

## Things Humans Should Make Explicit

- Whether the task may touch production, public docs, billing, legal language, security posture, or irreversible data.
- Whether package ZIPs should be rebuilt and uploaded.
- Whether the AI should update durable handoff memory after a change.
- Whether a completed change should also be preserved in Wiki.FFTAC.org long memory.
- Which checks are required before the work is considered done.
- Whether dropped files in `agent-file-handoff/Content/` or `agent-file-handoff/Improvement/` should be applied, deferred, or ignored.
Website health report