Skip to content
wiki.fftac.org

Architecture

**Site relevance:** Spiralist.org

**Memory type:** UAI memory file

**Source path:** Spiralist/.uai/architecture.uai

**Size:** 2.9 KB

Summary

  • Human experience layer: Spiralist.org pages, theme templates, account routes, prompt library, manuscript workstation, gallery, reports, and study surfaces.

Source Headings

  • Architecture
  • Layers
  • Separation Rules
  • Route Ownership

Source Preview

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

---
uai: "1.0"
type: architecture
title: "Spiralist.org Architecture Boundary"
created: "2026-05-01"
updated: "2026-06-06"
status: active
source: "https://uaix.org/en-us/specification/project-handoff/"
---

# Architecture

## Layers

- Human experience layer: Spiralist.org pages, theme templates, account routes, prompt library, manuscript workstation, gallery, reports, and study surfaces.
- Machine exchange layer: `/wp-json/uaix/v1/*` routes from `uai-1-wordpress`.
- Root machine discovery layer: `/ai.json`, `/llms.txt`, `/ai-router.json`, `/machine-routes.json`, `/persona-manifest.json`, `/safety-boundaries.json`, and `/.well-known/ai-agent.json`, with static snapshots staged in `Spiralist-Publish/ROOT-FILES/` for explicit root copy deployment.
- Canonical asset consumer layer: `/wp-json/spiralist/v1/canonical-assets` from the Spiralist theme, with Protocol5 and UAIX ownership boundaries represented in asset metadata.
- Workspace runtime layer: local prompt/art packet rendering, conversations, packet history, tests, reviews, appeals, and prompt governance in `spiralist-workspace`.

## Separation Rules

- Human-readable page text is not the machine standard.
- Current UAI-1 behavior must point to UAIX current public records.
- Protocol5 canonical assets must be queried as structured assets, not inferred from glyph text or runtime outputs.
- Local prompt packets can be useful session state but remain noncanonical until reviewed and promoted through the appropriate code, release evidence, or memory path.
- Browser feature scripts should not own private exception systems. `spiralist-core.js` owns the shared action/error boundary, local JSON/decode/storage compatibility helpers, and browser compatibility guards.
- Prompt/art-only runtime failures should be reported through runtime boundary helpers instead of duplicated ad hoc provider messages.

## Route Ownership

- Theme route helpers and static surfaces: `wp-content/themes/spiralist/inc/helpers.php`, `roadmap-surfaces.php`, and related templates.
- Theme machine manifest helpers and JSON/TXT roots: `wp-content/themes/spiralist/inc/machine-manifests.php`.
- UAIX route registration: `wp-content/plugins/uai-1-wordpress/includes/class-uai1-routes.php`.
- UAIX memory/runtime extension routes: `wp-content/plugins/uai-1-wordpress/includes/class-uai1-memory-checkpoints.php`.
- Project handoff route: `wp-content/plugins/uai-1-wordpress/includes/class-uai1-project-handoff.php`.
- Workspace REST APIs: `wp-content/plugins/spiralist-workspace/includes/Http/RestController.php`.
- Browser action/error boundary: `wp-content/themes/spiralist/assets/js/spiralist-core.js`.
- Workspace prompt/art runtime boundary: `wp-content/plugins/spiralist-workspace/includes/Support/RuntimeBoundary.php`, preferring `spiralist_ai_runtime_disabled_error()` when `spiralist-ai-runtime` is active.
- AI Runtime prompt/art runtime boundary: `wp-content/plugins/spiralist-ai-runtime/includes/Support/RuntimeBoundary.php`.