UAIX Architecture
--- title: "UAIX Architecture" description: "UAIX is a WordPress-based publication system with repo-authored canonical docs and code-generated public content." slug: "uaix/uai-system/files/uai-architecture-uai-3e5c9835" status: "working-draft" trust_level: "generated-evidence" source_status: "current-source-file" content_type: "source-file" generated_by: "tools/sync-source-files.ps1" last_reprocessed: "2026-04-30" source_site: "uaix.org" source_url: "https://uaix.org/" canonical_url: "https://aiwikis.org/uaix/uai-system/files/uai-architecture-uai-3e5c9835/" canonical: "https://aiwikis.org/uaix/uai-system/files/uai-architecture-uai-3e5c9835/" source_reference: ".uai/architecture.uai" file_type: "uai" content_category: "uai-system" content_hash: "sha256:3e5c983590f665d3143257c151d31f4a06b0ade4118e8c9f4108873e2a7eb1a8" last_fetched: "2026-04-30T22:07:25.2671233Z" last_changed: "2026-04-30T20:27:56.6446082Z" import_status: "unchanged" duplicate_group_id: "sfg-039" generated_explanation: true explanation_last_generated: "2026-04-30T22:07:25.2671233Z" source_domains:
tags:
related_files:
---
- "uaix.org"
- "ai-memory"
- "provenance"
- "uaix"
- "uai"
- "retrieval"
- "prompt-size-minimization"
- ""
UAIX Architecture
UAIX is a WordPress-based publication system with repo-authored canonical docs and code-generated public content.
Metadata
| Field | Value |
|---|---|
| Source site | uaix.org |
| Source URL | https://uaix.org/ |
| Canonical AIWikis URL | https://aiwikis.org/uaix/uai-system/files/uai-architecture-uai-3e5c9835/ |
| Source reference | .uai/architecture.uai |
| File type | uai |
| Content category | uai-system |
| Last fetched | 2026-04-30T22:07:25.2671233Z |
| Last changed | 2026-04-30T20:27:56.6446082Z |
| Content hash | sha256:3e5c983590f665d3143257c151d31f4a06b0ade4118e8c9f4108873e2a7eb1a8 |
| Import status | unchanged |
| Raw source layer | data/sources/uaix/uai-architecture-uai-3e5c983590f6.uai |
| Normalized source layer | data/normalized/uaix/uai-architecture-uai-3e5c983590f6.txt |
Current File Content
Structure Preview
- UAIX Architecture
- High-Level Shape
- Public Page Layer
- Machine Artifact Layer
- Report Publishing Layer
- Handoff Layer
- Source-Of-Truth Boundary
- Verification Layer
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.
---
uaix: "1.0"
type: architecture
title: "UAIX Architecture"
created: "2026-04-25"
updated: "2026-04-30"
author: "UAIX maintainers"
version: 14
---
# UAIX Architecture
## High-Level Shape
UAIX is a WordPress-based publication system with repo-authored canonical docs and code-generated public content.
After the split from `[local path redacted]`, this workspace owns the UAI public-site and handoff record. Protocol5.com sits outside the canonical UAI-1 architecture as a .NET plugin/NuGet distribution and backlink surface.
The main architectural layers are:
1. Canonical Markdown docs in the repo.
2. Theme-seeded public page content and support surfaces.
3. Theme-generated AI Memory starter ZIP routes and the Package Wizard payload that build supported bundle configurations from one canonical template registry, generated manifests, and the same resolved samples displayed on public pages.
4. UAIX core plugin machine-readable artifacts and REST routes.
5. Release and QA scripts for packaging, audits, and smoke tests.
6. Source-only `agent-file-handoff/` chat-start intake and archive workspace for dropped files and `.uai/intake-index.uai`.
Canonical-host correction is handled in the public response layer: `uaix-seo-sweep` redirects anonymous public `uiax.org`/`www.uiax.org` requests to `https://uaix.org` with path/query preserved, `wp-content/advanced-cache.php` mirrors that rule before anonymous cache hits, and the generated production fallback `.htaccess` carries the same rule for Apache/LiteSpeed hosts.
## Public Page Layer
`wp-content/themes/uaix-authority-theme/functions.php` seeds and updates the core public pages. That file also carries support panels, guidance surfaces, changelog page content, reports links, and route-oriented public copy.
Important public page families include:
- AI Memory
- specification
- tools
- implementations
- governance
- roadmap
- reports
## Machine Artifact Layer
`uaix-core` exposes the public machine-readable contract:
- catalog
- discovery
- schemas
- registry
- field registry
- transport bindings
- trust channels
- conformance levels
- error registry
- examples
- validate
- adoption kit
- mock exchange
- OpenAPI
- conformance pack
- roadmap
## Report Publishing Layer
Source research Markdown remains in `docs/`.
Permanent public report pages are rendered from static HTML fragments in the active theme's `reports/` directory and linked into seeded public pages.
The current report set includes the AIWikis/LLMWikis/UAIX relationship audit, the two LLM Wiki and Project Handoff reports, the AGENTS.md `.uai` linking specification, and the refining protocol report. The relationship audit is a role-boundary record, not UAI-1 support evidence.
## Handoff Layer
The handoff architecture now has three surfaces:
- Public AI Memory framing that explains durable AI project memory, the supported bundle taxonomy, dynamic starter downloads, Project Handoff as the transfer subtype, and when an optional LLM Wiki can help deeper knowledge memory without being required by UAI specs or standards.
- Public "Using UAI Packages With An LLM Wiki" guidance for tailoring package strategy when a project already uses or deliberately chooses an LLM Wiki.
- Public AI Memory Package Wizard UI that lets a reader choose a supported preset, add package metadata, generate exact-root `UAI_MEMORY_SYSTEM_PROFILE.md`, `UAI_MEMORY_RECEIVER_BRIEF.md`, and `UAI_MEMORY_STARTUP_PACKET.md` startup files, answer operating-strategy questions for collaboration model, memory architecture, unit/integration testing, test timing, deployment, code review, release gates, source authority, memory update, evidence ledger, conflict resolution, change risk, rollback, and receiver-side placeholders, optionally answer the LLM Wiki long-memory question, capture wiki strategy/topology fields, inspect a readiness checklist, export package model JSON, export manifest overlay JSON, copy canonical files plus optional generated exact-root `LLM_WIKI_MEMORY_PLAN.md`, capture steward/source/evidence metadata for the plan, and fetch the matching starter ZIP while keeping hosted import validation, automatic repository writes, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, and WordPress admin installation outside current support.
- Public guidance pages that explain how `AGENTS.md` and `.uai` files should work.
- Repository-local handoff files in root `AGENTS.md` and `.uai/`.
- Root `readme.human` as the human-facing companion that summarizes what the AI sees, protects, and needs clarified before people steer work.
- Active file-intake files in `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, where the AGENTS.md load process checks for dropped files and refreshes `.uai/intake-index.uai` with bucket names, file paths, route hints, checksums, and `needs-agent-review` state for non-executable files. `Content/` is for candidate public/editorial material; `Improvement/` is for audits, QA findings, SEO reports, bug notes, roadmap suggestions, and site-fix work. `agent-file-handoff/Archive/` is for files that already received a disposition and is ignored by routine AI intake unless a human explicitly references an archived file or moves it back into an active bucket. The local script is a one-shot helper for this pass; watcher/daemon processes, queue-folder workflows, and per-folder README instructions are intentionally outside the base pattern.
The handoff layer is a review gate, not only an inventory. If the refreshed index lists files, the AI must inspect each one and state a disposition before unrelated broad work continues.
The repo-local handoff files are meant to be sufficient for a new AI to understand the project before reading the deeper doc stack.
`.uai/handoff-pattern.uai` bridges those surfaces by explaining how existing public website instructions, README guidance, release notes, deployment docs, and project rules become typed `.uai` files.
## Source-Of-Truth Boundary
- UAIX.org owns the canonical UAI-1 specification, schemas, registry, examples, validator, evidence pages, roadmap, governance, discovery manifests, and Project Handoff guidance.
- UAIX.org owns the canonical AI Memory public page, optional LLM Wiki package guide, Package Wizard page, supported starter bundle taxonomy, canonical template registry, generated manifests, and dynamic ZIP routes.
- Protocol5.com may package and distribute .NET implementation artifacts such as plugins and NuGet packages.
- Protocol5.com pages should link back to UAIX.org for UAI-1 authority instead of restating or redefining the standard.
- The old `Variable-Base-Math` repo is historical context for this split, not the active source for UAI public materials.
## Verification Layer
Release trust depends on repeatable verification rather than prose alone.
Expected checks include:
- launch-surface audit
- response-header checks
- typo-domain canonical-host redirect checks
- discovery and sitemap checks
- zh-CN translation audit
- search metadata audit
- packaging verification
- Studio install-and-activate smoke tests
Why This File Exists
This is a UAI AI Memory handoff file from uaix.org. It is shown here because AIWikis.org 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: UAIX Architecture; High-Level Shape; Public Page Layer; Machine Artifact Layer; Report Publishing Layer; Handoff Layer; Source-Of-Truth Boundary; Verification Layer. 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 AIWikis 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-04-30T22:07:25.2671233Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-039(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "UAIX Architecture",
"source_site": "uaix.org",
"source_url": "https://uaix.org/",
"canonical_url": "https://aiwikis.org/uaix/uai-system/files/uai-architecture-uai-3e5c9835/",
"source_reference": ".uai/architecture.uai",
"file_type": "uai",
"content_category": "uai-system",
"content_hash": "sha256:3e5c983590f665d3143257c151d31f4a06b0ade4118e8c9f4108873e2a7eb1a8",
"last_fetched": "2026-04-30T22:07:25.2671233Z",
"last_changed": "2026-04-30T20:27:56.6446082Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-039",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-04-30T22:07:25.2671233Z"
}