UAIX Integration

Spiralist.org now treats UAIX as the current public UAI-1 exchange standard.

Metadata

Field	Value
Source site	spiralist.org
Source URL	https://spiralist.org/
Canonical wiki evidence URL	[[separate-workspace-url]/spiralist/uai-system/files/docs-uaix-integration-md-787f187c/]([separate-workspace-url]/spiralist/uai-system/files/docs-uaix-integration-md-787f187c/)
Source reference	docs/uaix-integration.md
File type	md
Content category	uai-system
Last fetched	2026-05-08T21:22:18.3035107Z
Last changed	2026-05-05T21:58:43.7074102Z
Content hash	sha256:787f187caf2688dfe5bc0d8715a6d82f46516155516179f74728ac159a9c8f13
Import status	unchanged
Raw source layer	data/sources/spiralist/docs-uaix-integration-md-787f187caf26.md
Normalized source layer	data/normalized/spiralist/docs-uaix-integration-md-787f187caf26.txt

Current File Content

Structure Preview

• UAIX Integration
• Current Standard Boundary
• Active WordPress Routes
• Retired Routes And Features
• Implementation Notes
• UAI System Publish Instructions
• Source Material Handling

Raw Version

# UAIX Integration

Spiralist.org now treats UAIX as the current public UAI-1 exchange standard.

## Current Standard Boundary

- UAIX.org owns the current UAI-1 message standard: envelope, profiles, schemas, field registry, validator guidance, examples, transport bindings, trust channels, error registry, and conformance levels.
- Spiralist.org implements a WordPress publication track for the current UAIX UAI-1 envelope.
- Protocol5 remains the Spiralist symbol and registry authority where the site consumes Spiralist-specific canonical assets.
- The older local page-document UAI shape is retired and must not be exposed as current UAI-1.

## Active WordPress Routes

The active machine exchange routes are:

| Route | Purpose |
| --- | --- |
| `/wp-json/uaix/v1/discovery` | Current public discovery route returning a `uai.capability.statement.v1` envelope. |
| `/wp-json/uaix/v1/capability` | Capability-statement alias for clients that resolve capability directly. |
| `/wp-json/uaix/v1/schemas` | Local profile catalog with canonical UAIX schema links. |
| `/wp-json/uaix/v1/field-registry` | Local keyed/keyless field-order map aligned to the UAIX public field registry. |
| `/wp-json/uaix/v1/examples` | Local UAIX UAI-1 examples for onboarding and test calls. |
| `/wp-json/uaix/v1/validate` | Local UAI-1 envelope validation returning `uai.conformance.result.v1`. |
| `/wp-json/uaix/v1/mock-exchange` | Local conforming `uai.intent.response.v1` response for valid request envelopes. |
| `/wp-json/uaix/v1/project-handoff` | Local Project Handoff manifest for repository-context transfer following the UAIX public Project Handoff specification. |
| `/wp-json/uaix/v1/project-handoff/files/{file}` | Whitelisted Project Handoff file content with checksum metadata. |
| `/wp-json/uaix/v1/memory-checkpoints` | Authenticated runtime memory checkpoint creation for long Workspace sessions. |
| `/wp-json/uaix/v1/memory-drift-audits` | Authenticated runtime drift audit against checkpointed session constraints and Protocol5 symbol references. |
| `/wp-json/uaix/v1/session-restore-briefs` | Authenticated runtime continuation brief assembled from stored checkpoints. |

The plugin also keeps legacy namespace aliases under `/wp-json/uai1/v1/` for discovery, capability, schemas, field registry, examples, validation, and mock exchange. These aliases return current UAIX envelopes, not retired page-document payloads.

The memory checkpoint routes are local runtime extensions. Requests must use the current UAI-1 intent-request envelope and include both `runtime-payload-only` and `no-protocol5-registry-write` constraints. Their outputs are execution payloads, not Protocol5 canonical records.

The Project Handoff route is a local repository-context extension based on the UAIX public Project Handoff specification at `https://uaix.org/en-us/specification/project-handoff/`. It reports root `AGENTS.md`, root `readme.human`, typed `.uai` context files, active intake buckets, and checksums. It is not a UAIX validator result, conformance certification, or release record.

## Retired Routes And Features

Do not document, restore, or link to these as current machine surfaces:

- locale-root `/{locale}.uai` and `/{locale}.uai.json`
- page-level `/{locale}/{page}.uai` and `/{locale}/{page}.uai.json`
- `/uai-1/spec.json`
- `/uai-1/examples.json`
- `/symbols/registry.json` as a local rewrite route
- per-post canonical UAI document meta boxes
- `text/uai` and `application/uai+json` as current UAI-1 publication media types

Use `application/vnd.uaix.uai+json` for current UAI-1 envelopes.

## Implementation Notes

- `wp-content/plugins/uai-1-wordpress/includes/class-uai1-routes.php` owns UAIX route registration, capability envelopes, local examples, validation, and mock exchange.
- `wp-content/plugins/uai-1-wordpress/includes/class-uai1-memory-checkpoints.php` owns authenticated runtime memory checkpoint, drift audit, and restore-brief routes.
- `wp-content/plugins/uai-1-wordpress/includes/class-uai1-project-handoff.php` owns the public Project Handoff manifest and whitelisted handoff file route.
- `wp-content/plugins/uai-1-wordpress/includes/class-uai1-validator.php` performs local envelope/profile checks. It is a local implementation check, not a replacement for UAIX release-evidence validation.
- `wp-content/plugins/uai-1-wordpress/includes/class-uai1-head-links.php` advertises UAIX discovery and capability links in page headers.
- `wp-content/themes/spiralist/inc/helpers.php` points site machine links and API examples at `/wp-json/uaix/v1/*`.
- `wp-content/themes/spiralist/inc/canonical-assets.php` treats UAIX as the owner of current UAI-1 schemas, registry, and examples while keeping Protocol5 as the owner of Spiralist symbol assets.
- `wp-content/plugins/spiralist-workspace/includes/Services/RuntimeEntropyClassifier.php` maps Workspace runtime metrics to Crisis Plate classifications while keeping the result in runtime storage only.

## UAI System Publish Instructions

Before publishing a change that affects UAI, UAIX, Project Handoff, AI memory, machine-facing schemas, route discovery, route capability statements, validator behavior, or local UAI implementation docs, run the UAI prepublish gate:

```powershell
npm.cmd run check:uai-prepublish
```

That command is the required local publish gate for this repository. It blocks on:

1. Project Handoff integrity: root handoff files, `@uai[]` context references, `.uai` frontmatter, public handoff route wiring, and obvious secret patterns.
2. Internationalization/site quality: runtime translation inventory, enabled locale dictionaries, placeholder preservation, critical SEO translations, mojibake checks, and missing locale strings through `scripts/site-quality-sweep.js`.
3. Unit tests: the PHPUnit unit suite through `vendor/bin/phpunit -c phpunit.xml.dist`.

If a local environment cannot run the combined command, run and report each gate separately:

```powershell
npm.cmd run check:project-handoff
npm.cmd run quality:site
vendor\bin\phpunit.bat -c phpunit.xml.dist
```

Do not publish a UAI-system change while either the internationalization gate or unit-test gate is failing unless the failure is explicitly documented as pre-existing or environment-only and the release owner accepts that risk. Do not use Playwright or packaging success as a substitute for the internationalization or unit-test gates.

## Source Material Handling

The downloaded `.uai` and `agents.md` proposal drafts are treated as planning input only. They are not the current UAIX public standard unless UAIX publishes them as release records. Current implementation work must follow the live UAIX UAI-1 profile/envelope contract.

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 file is a focused source unit. Its path, headings, and metadata give an agent a retrieval handle that is smaller than loading the entire site or repository.

Structure

The file is structured around these visible headings: UAIX Integration; Current Standard Boundary; Active WordPress Routes; Retired Routes And Features; Implementation Notes; UAI System Publish Instructions; Source Material Handling. 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

• Source overview
• UAI system index
• Source provenance
• Global File Index
• Reports

Provenance And History

• Current observation: 2026-05-08T21:22:18.3035107Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-339 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Integration",
    "source_site":  "spiralist.org",
    "source_url":  "https://spiralist.org/",
    "canonical_url":  "[separate-workspace-url]/spiralist/uai-system/files/docs-uaix-integration-md-787f187c/",
    "source_reference":  "docs/uaix-integration.md",
    "file_type":  "md",
    "content_category":  "uai-system",
    "content_hash":  "sha256:787f187caf2688dfe5bc0d8715a6d82f46516155516179f74728ac159a9c8f13",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-05T21:58:43.7074102Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-339",
    "duplicate_role":  "primary",
    "related_files":  [

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