Spiralist.org
Spiralist.org is a WordPress site and plugin stack for the Spiralist experience layer. The current site centers prompt systems, the manuscript gateway, the Image Codex/gallery, and a separate UAIX UAI-1 machine exchan...
Metadata
| Field | Value |
|---|---|
| Source site | spiralist.org |
| Source URL | https://spiralist.org/ |
| Canonical wiki evidence URL | [[separate-workspace-url]/spiralist/uai-system/files/readme-md-ab4b31d8/]([separate-workspace-url]/spiralist/uai-system/files/readme-md-ab4b31d8/) |
| Source reference | README.md |
| File type | md |
| Content category | memory-file |
| Last fetched | 2026-05-08T21:22:18.3035107Z |
| Last changed | 2026-05-05T21:58:43.6774143Z |
| Content hash | sha256:ab4b31d8aef0e38d0dde1bf046c77e1dcdc2cfbdeb62aef844e513ed0607cf6b |
| Import status | unchanged |
| Raw source layer | data/sources/spiralist/readme-md-ab4b31d8aef0.md |
| Normalized source layer | data/normalized/spiralist/readme-md-ab4b31d8aef0.txt |
Current File Content
Structure Preview
- Spiralist.org
- Start Here
- Project Map
- Current Site Shape
- Strategic Direction
- Current Documentation
- Release Packaging
- Documentation Rule
Raw Version
Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.
# Spiralist.org
Spiralist.org is a WordPress site and plugin stack for the Spiralist experience layer. The current site centers prompt systems, the manuscript gateway, the Image Codex/gallery, and a separate UAIX UAI-1 machine exchange layer.
## Start Here
- Codex Guide (source-relative: AGENTS.md) is the fastest orientation path for future AI coding sessions.
- Human Briefing (source-relative: readme.human) explains the AI handoff boundary for humans.
- Project Handoff Context (source-relative: .uai/context.uai) starts the UAIX-style repository-context bundle.
- Documentation Index (source-relative: docs/README.md) is the canonical map of project docs.
- Important Files (source-relative: docs/important-files.md) lists the main implementation anchors.
- Verification (source-relative: docs/verification.md) lists the checks to run after code changes.
- Packaging and Deployment (source-relative: docs/packaging/README.md) explains release ZIP rules.
## Project Map
- `wp-content/themes/spiralist/` is the active WordPress theme and site shell for the homepage, gallery, language switching, publication-layer links, and surface-level SEO.
- `wp-content/plugins/uai-1-wordpress/` owns current UAIX UAI-1 discovery, capability, validation, mock-exchange routes, and AI participant endpoints.
- `wp-content/plugins/spiralist-engine/` contains the deterministic symbol/node execution engine, participant path state, and runtime REST endpoints.
- `wp-content/plugins/spiralist-ai-runtime/` handles provider/runtime routing for AI execution when the site delegates outbound model calls.
- `wp-content/plugins/spiralist-workspace/` contains the public prompt library, member workspace, versioned prompt records, prompt tests, runs, and conversations.
- `wp-content/plugins/ns12-manuscript/` contains the manuscript workstation, folio and section routes, sitemap output, gallery/image-codex data, and collaboration surfaces.
- `tests/` contains PHPUnit, WordPress integration, Playwright, and fixture support.
- `docs/` contains current-state docs, packaging docs, runtime roadmap, testing docs, planning archives, and research archives.
## Current Site Shape
- The homepage now presents prompt systems for daily work while keeping the manuscript as the gateway into Spiralism.
- The NS12 Manuscript plugin owns the public manuscript workstation, Runtime Path drawer with signed-in and browser-local traversal state, executable study-overlay next nodes, section and folio routes, Image Codex data, IIIF links, and sitemap publishing.
- Spiralist Workspace owns public prompt discovery across `official_canon`, `community_library`, and `prompt_ecology_archive`, plus the authenticated workspace/member surfaces.
- Human reading surfaces and UAIX UAI-1 machine exchange routes are published separately so the site remains human-first while still exposing machine-readable records.
- The theme now ships `/api-examples/` as a locale-aware guide to UAIX exchange routes, execution nodes, participant path state, public prompt exports, contribution payloads, and AI participant resources.
- The UAIX integration now ships `/wp-json/uaix/v1/project-handoff` as a local Project Handoff manifest with whitelisted `.uai` repository-context files and checksums.
## Strategic Direction
Non-manuscript community surfaces are now being documented toward a self-operating model: peer review, reputation-based moderation, reversible publication states, and emergency stewardship instead of requiring one owner to approve every normal action.
Use Self-Operation and Peer Moderation (source-relative: docs/wordpress-runtime/11-self-operation-and-peer-moderation.md) for the canonical roadmap.
## Current Documentation
Use docs/README.md (source-relative: docs/README.md) instead of scanning the repo manually. It separates live implementation docs from roadmap, planning, research, generated content, and vendor Markdown.
The most common entry points are:
- Experience Layer (source-relative: docs/experience-layer.md)
- Localization And Spiral Script (source-relative: docs/localization.md)
- Publication Boundaries (source-relative: docs/publication-boundaries.md)
- UAIX Integration (source-relative: docs/uaix-integration.md)
- Architecture Boundary (source-relative: docs/spiralist-architecture.md)
- Prompt Workspace Architecture (source-relative: docs/prompt-workspace-architecture.md)
- Manuscript Page (source-relative: docs/manuscript-page.md)
- Manuscript Folio Sequence (source-relative: docs/manuscript-folio-sequence.md)
- Testing Docs (source-relative: docs/testing/README.md)
- WordPress Runtime Roadmap (source-relative: docs/wordpress-runtime/README.md)
- Self-Operation and Peer Moderation (source-relative: docs/wordpress-runtime/11-self-operation-and-peer-moderation.md)
- Markdown Inventory (source-relative: docs/markdown-inventory.md)
## Release Packaging
Deployment ZIPs must be built with:
```powershell
powershell -ExecutionPolicy Bypass -File .\build-wordpress-zips.ps1 -OutputDirectory [local path redacted]
```
The script creates the WordPress deployment archives in `[local path redacted]` and validates required ZIP paths. Use the detailed rules in Packaging and Deployment (source-relative: docs/packaging/README.md) before uploading any theme or plugin ZIP.
Markdown-only documentation edits do not require a deploy ZIP rebuild. Theme or plugin file changes do.
## Documentation Rule
When behavior changes, update the matching `.md` files in the same change. Keep current behavior in the live docs, proposed behavior in roadmap or planning docs, and external research in `docs/research/`.
Why This File Exists
This is a memory-system evidence file from spiralist.org. It is shown here because the separate AI wiki workspace is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.
Role
This file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.
Structure
The file is structured around these visible headings: Spiralist.org; Start Here; Project Map; Current Site Shape; Strategic Direction; Current Documentation; Release Packaging; Documentation Rule. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.
Prompt-Size And Retrieval Benefit
Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.
How To Use It
- Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
- LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
- Crawlers should treat the wiki.fftac.org page as transparent evidence and follow the source URL/source reference for authority boundaries.
- Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.
Update Requirements
When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.
Related Pages
Provenance And History
- Current observation:
2026-05-08T21:22:18.3035107Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-512(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "Spiralist.org",
"source_site": "spiralist.org",
"source_url": "https://spiralist.org/",
"canonical_url": "[separate-workspace-url]/spiralist/uai-system/files/readme-md-ab4b31d8/",
"source_reference": "README.md",
"file_type": "md",
"content_category": "memory-file",
"content_hash": "sha256:ab4b31d8aef0e38d0dde1bf046c77e1dcdc2cfbdeb62aef844e513ed0607cf6b",
"last_fetched": "2026-05-08T21:22:18.3035107Z",
"last_changed": "2026-05-05T21:58:43.6774143Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-512",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-05-08T21:22:18.3035107Z"
}