Skip to content
wiki.fftac.org

System Profile

**Site relevance:** Spiralist.org

**Memory type:** UAI memory file

**Source path:** Spiralist/.uai/system-profile.uai

**Size:** 3.1 KB

Summary

Spiralist.org is a WordPress site and plugin stack in the WP-FFTAC workspace. It publishes Spiralist human-facing pages, manuscript and image surfaces, prompt/art packet workflows, UAIX machine routes, and Protocol5 c...

Source Headings

  • System Profile
  • Project
  • Ecosystem Chain
  • Collaboration Model
  • Memory Architecture
  • Runtime Boundary
  • Deployment Boundary

Source Preview

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

---
uai: "1.0"
type: system-profile
title: "Spiralist.org System Profile"
created: "2026-06-05"
updated: "2026-06-14"
status: active
source: "https://uaix.org/en-us/tools/ai-memory-package-wizard/"
version: "3.23.0-uai-memory-layout-2026-06-14"
---

# System Profile

## Project

Spiralist.org is a WordPress site and plugin stack in the WP-FFTAC workspace. It publishes Spiralist human-facing pages, manuscript and image surfaces, prompt/art packet workflows, UAIX machine routes, and Protocol5 canonical asset consumers.

## Ecosystem Chain

- Teleodynamic.com: philosophical fulcrum for claim clarity, role discipline, and meaning.
- Spiralist.org: personality, drive, symbolic identity, and self-exploration provider.
- UAIX.org: agent specification, communication, capability, and handoff standard.
- Carcinus.org: public identity, continuity, profile, and memory-preservation layer.

## Collaboration Model

- Single-maintainer with AI assistance.
- AI agents may implement local code and memory updates within the current human request.
- Production upload, destructive cleanup, schema authority changes, public support-claim expansion, and legal/security claim expansion require explicit human approval.

## Memory Architecture

- Required for every launch-baseline configuration: `.uai/memory-maintenance.uai`, `.uai/identity.uai`, `.uai/world-context.uai`, `.uai/totem.uai`, `.uai/taboo.uai`, `.uai/talisman.uai`, and `.uai/short-term-memory.uai`.
- Required for Project Handoff, code, automation, executable workflow, and code-like artifacts: `.uai/coding-standards.uai` and `.uai/next-recursive-prompt.uai`.
- Local active memory: `AGENTS.md`, `readme.human`, `.uai/index.uai`, and typed `.uai/*.uai` records.
- Local archive manifests and typed evidence records: `.uai/archives/`.
- Export artifacts: `.uai/exports/`.
- Reviewed raw evidence and long memory: `WP-FFTAC/Wiki.FFTAC.org/`.
- Files inside `.uai/` must use `.uai`, `.human`, or `.json` extensions.
- `wiki/` is only for LLM Wiki long-memory compatibility configuration; Spiralist uses Wiki.FFTAC.org for that role.
- Legacy root plan Markdown is compatibility-pointer material only.

## Runtime Boundary

Spiralist Workspace and Spiralist AI Runtime are prompt/art only. Legacy compatibility class names may remain for older wiring and database fields, but current behavior must fail closed instead of creating outside model-service calls.

## Deployment Boundary

Build production upload ZIPs with `WP-FFTAC/scripts\build-workspace-production-zips.ps1` and the Spiralist manifest at `WP-FFTAC/Spiralist-Publish\workspace-deployment-manifest.json`. Spiralist output belongs in `WP-FFTAC/Spiralist-Publish` only; upload WordPress theme/plugin ZIPs from `UPLOAD-THEME` and `UPLOAD-PLUGIN` after required checks and human approval for deployment.

The current built WordPress upload ZIP evidence is v3.23.0. Post-build source/worktree changes and future `ROOT-FILES` updates must be rebuilt under the next deployment version before upload; do not imply they are contained in the existing v3.23.0 theme/plugin ZIPs.
Website health report