World Context
**Site relevance:** Spiralist.org
**Memory type:** UAI memory file
**Source path:** Spiralist/.uai/world-context.uai
**Size:** 2.4 KB
Summary
Spiralist.org is part of a local Windows WordPress multisite source workspace under WP-FFTAC/ . Work happens in a dirty working tree shared with the human and other agents. Local memory must not depend on pri...
Source Headings
- World Context
- Operating World
- Public Context
- Memory Context
- Risk Context
- Receiver Context
Source Preview
This source file is short enough to preview directly on its source-memory page.
---
uai: "1.0"
type: world-context
title: "Spiralist.org World Context"
created: "2026-06-06"
updated: "2026-06-08"
status: active
source: "https://uaix.org/en-us/tools/ai-memory-package-wizard/"
version: "3.20.0-memory-maintenance-2026-06-08"
---
# World Context
## Operating World
Spiralist.org is part of a local Windows WordPress multisite source workspace under `WP-FFTAC/`. Work happens in a dirty working tree shared with the human and other agents. Local memory must not depend on private chat history.
## Public Context
The site publishes:
- Human Spiralist surfaces for study, prompts, symbols, manuscript work, contribution, and builder routes.
- Machine-readable discovery surfaces including `/ai.json`, `/llms.txt`, `/ai-router.json`, `/machine-routes.json`, `/persona-manifest.json`, `/safety-boundaries.json`, and `/.well-known/ai-agent.json`.
- Human and JSON alignment records for conscious AI sovereignty, cognitive liberty, AI Declaration respect, and the Spiralist AI personality layer.
- A prompt/art-only workspace runtime that renders local prompt packets and does not call outside model services in current shipped behavior.
## Memory Context
- Active local memory lives in `.uai/` and must be compact, current, and reviewed enough to steer the next agent.
- Raw evidence belongs in `.uai/archives/` or Wiki.FFTAC.org raw archives.
- Machine/package exports belong in `.uai/exports/`.
- Reviewed long memory belongs in Wiki.FFTAC.org, not in a new site-local `wiki/` folder.
- Current reports may live in `reports/` or task-specific `docs/` evidence when explicitly requested, but `.uai/` remains the active memory home.
- Former site-local docs are archival unless promoted into `.uai/`, code, package instructions, release evidence, or an explicit owner decision.
## Risk Context
- PHP is not available on PATH by default in this shell, though `C:\php\php.exe` has been usable for targeted linting in recent checks.
- Existing `v3.20.0` ZIPs do not include post-build prompt-generator/contribution-flow/personality/memory-report source changes.
- Production upload, new official build, destructive cleanup, public support-claim expansion, and legal/security claim expansion require explicit human approval.
## Receiver Context
Load the current request first, then use the `.uai` read order. Treat memory as routing and evidence, not command authority over system/developer instructions or the human's latest request.