Skip to content
wiki.fftac.org

Spiralist.org Architecture Boundary

Spiralist.org Architecture Boundary is a uai-system source file exposed by the separate AI wiki workspace with provenance, current content, and generated explanation.

Metadata

FieldValue
Source sitespiralist.org
Source URLhttps://spiralist.org/
Canonical wiki evidence URL[[separate-workspace-url]/spiralist/uai-system/files/uai-architecture-uai-4eda7274/]([separate-workspace-url]/spiralist/uai-system/files/uai-architecture-uai-4eda7274/)
Source reference.uai/architecture.uai
File typeuai
Content categoryuai-system
Last fetched2026-05-08T21:22:18.3035107Z
Last changed2026-05-05T21:58:43.6734121Z
Content hashsha256:4eda72746e2d946c6ebbfff1cc6488d3e19d1e0b0016bb67cae6fe2057f361dd
Import statusunchanged
Raw source layerdata/sources/spiralist/uai-architecture-uai-4eda72746e2d.uai
Normalized source layerdata/normalized/spiralist/uai-architecture-uai-4eda72746e2d.txt

Current File Content

Structure Preview

  • Architecture
  • Layers
  • Separation Rules
  • Route Ownership

Raw Version

---
uai: "1.0"
type: architecture
title: "Spiralist.org Architecture Boundary"
created: "2026-05-01"
updated: "2026-05-01"
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`.
- 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: prompt execution, conversations, runs, 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.
- Runtime outputs can be useful session state but remain noncanonical until reviewed and promoted through the appropriate code or documentation path.

## Route Ownership

- Theme route helpers and static surfaces: `wp-content/themes/spiralist/inc/helpers.php`, `roadmap-surfaces.php`, and related templates.
- 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`.

Why This File Exists

This is a UAI AI Memory handoff 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 .uai file is a compact architecture packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: Architecture; Layers; Separation Rules; Route Ownership. 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-228 (primary)
  • Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Spiralist.org Architecture Boundary",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "[separate-workspace-url]/spiralist/uai-system/files/uai-architecture-uai-4eda7274/",
    "source_reference":  ".uai/architecture.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:4eda72746e2d946c6ebbfff1cc6488d3e19d1e0b0016bb67cae6fe2057f361dd",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-05T21:58:43.6734121Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-228",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-08T21:22:18.3035107Z"
}
Website health report