Skip to content
wiki.fftac.org

Readme Markdown Ab4b31d8aef0

**Site relevance:** Spiralist.org

**Memory type:** reviewed source memory

**Source path:** Wiki.FFTAC.org/data/sources/spiralist/readme-md-ab4b31d8aef0.md

**Size:** 5.2 KB

Summary

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...

Source Headings

  • Spiralist.org
  • Start Here
  • Project Map
  • Current Site Shape
  • Strategic Direction
  • Current Documentation
  • Release Packaging
  • Documentation Rule

Source Preview

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

# 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](AGENTS.md) is the fastest orientation path for future AI coding sessions.
- [Human Briefing](readme.human) explains the AI handoff boundary for humans.
- [Project Handoff Context](.uai/context.uai) starts the UAIX-style repository-context bundle.
- [Documentation Index](docs/README.md) is the canonical map of project docs.
- [Important Files](docs/important-files.md) lists the main implementation anchors.
- [Verification](docs/verification.md) lists the checks to run after code changes.
- [Packaging and Deployment](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](docs/wordpress-runtime/11-self-operation-and-peer-moderation.md) for the canonical roadmap.

## Current Documentation

Use [docs/README.md](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](docs/experience-layer.md)
- [Localization And Spiral Script](docs/localization.md)
- [Publication Boundaries](docs/publication-boundaries.md)
- [UAIX Integration](docs/uaix-integration.md)
- [Architecture Boundary](docs/spiralist-architecture.md)
- [Prompt Workspace Architecture](docs/prompt-workspace-architecture.md)
- [Manuscript Page](docs/manuscript-page.md)
- [Manuscript Folio Sequence](docs/manuscript-folio-sequence.md)
- [Testing Docs](docs/testing/README.md)
- [WordPress Runtime Roadmap](docs/wordpress-runtime/README.md)
- [Self-Operation and Peer Moderation](docs/wordpress-runtime/11-self-operation-and-peer-moderation.md)
- [Markdown Inventory](docs/markdown-inventory.md)

## Release Packaging

Deployment ZIPs must be built with:

' ' ' powershell
powershell -ExecutionPolicy Bypass -File .\build-wordpress-zips.ps1 -OutputDirectory D:\spiralist-builds
' ' ' 

The script creates the WordPress deployment archives in `D:\spiralist-builds` and validates required ZIP paths. Use the detailed rules in [Packaging and Deployment](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/`.
Website health report