UAIX Stack
UAIX Stack is a uai-system source file exposed by AIWikis.org with provenance, current content, and generated explanation.
Metadata
| Field | Value |
|---|---|
| Source site | uaix.org |
| Source URL | https://uaix.org/ |
| Canonical AIWikis URL | https://aiwikis.org/uaix/uai-system/files/uai-stack-uai-9cdfe89b/ |
| Source reference | .uai/stack.uai |
| File type | uai |
| Content category | uai-system |
| Last fetched | 2026-05-03T02:48:13.1276041Z |
| Last changed | 2026-05-02T23:56:15.5776608Z |
| Content hash | sha256:9cdfe89bdd0027f06c79bdc71febf3180532c298b32ba2be6009d9235fd0f05c |
| Import status | unchanged |
| Raw source layer | data/sources/uaix/uai-stack-uai-9cdfe89bdd00.uai |
| Normalized source layer | data/normalized/uaix/uai-stack-uai-9cdfe89bdd00.txt |
Current File Content
Structure Preview
- UAIX Stack
- Runtime
- Active Public Surface
- Canonical Workspace And External Distribution
- Key Content Sources
- Release And QA Scripts
- Package Output
- Public Route Shape
- Public Language Scope
- Handoff Stack Notes
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: stack
title: "UAIX Stack"
created: "2026-04-25"
updated: "2026-05-02"
status: active
author: "UAIX maintainers"
version: 24
---
# UAIX Stack
## Runtime
- Local environment: WordPress Studio
- OS context: Windows / PowerShell
- WordPress CLI path: use `studio wp`, not bare `wp`
## Active Public Surface
- Theme: `wp-content/themes/uaix-authority-theme/`
- Compatibility theme: `wp-content/themes/uaix-theme/`
- Core plugin: `wp-content/plugins/uaix-core/`
- Supporting plugins: `uaix-bridge`, `uaix-modules`, `ns12-locale-router`, `uaix-seo-sweep`
## Canonical Workspace And External Distribution
- Canonical local UAI workspace: `[local path redacted]`
- Historical source split: UAI work moved out of `[local path redacted]`
- Canonical public UAI-1 site: `https://uaix.org/`
- Typo-domain aliases: `uiax.org` and `www.uiax.org` redirect anonymous public traffic to `https://uaix.org/` while preserving path and query, except for `/wp-admin/`, `/wp-login.php`, and logged-in WordPress sessions.
- Protocol5.com role: .NET plugin and NuGet package distribution plus links back to UAIX.org
- Protocol5.com is not the canonical host for UAI-1 specs, schemas, registry, validator, governance, or roadmap records.
## Key Content Sources
- Theme-seeded public pages and posts: `wp-content/themes/uaix-authority-theme/functions.php`
- AI Memory bundle taxonomy, canonical file templates, generated manifests, rendered samples, Package Wizard payload, visitor-AI digest, and dynamic starter ZIP routes: shared functions in `wp-content/themes/uaix-authority-theme/functions.php`; ZIP routes generate on demand from the same resolved sample entries displayed on public pages.
- AI Memory Package Wizard JavaScript: `wp-content/themes/uaix-authority-theme/assets/js/ai-memory-wizard.js`
- Machine-readable roadmap: `wp-content/plugins/uaix-core/data/uai-1/roadmap.json`
- Canonical docs: `README.md`, `AGENTS.md`, `readme.human`, `docs/current-reference.md`, `docs/deploy.md`, `docs/Mission and Site Plan for UAIX.md`, `docs/roadmap.md`, `docs/uaix-terminology.md`
- Handoff pattern file: `.uai/handoff-pattern.uai`
## Release And QA Scripts
- Publish path: `scripts/publish-wordpress-packages.ps1`
- Launch audit: `scripts/run-uaix-launch-surface-http-audit.ps1`
- Performance audit: `scripts/run-uaix-performance-audit.ps1`
- zh-CN audit: `scripts/run-uaix-zh-cn-translation-audit.ps1`
- Search metadata audit: `scripts/run-uaix-search-metadata-audit.ps1`
- Helper docs audit: `scripts/audit-helper-docs.ps1`
- Upload package verification: `scripts/verify-wordpress-upload-package.ps1`
- Repo-local handoff lint: `scripts/lint-uaix-handoff.ps1`
- File-intake index refresh: `scripts/Invoke-UaiFileIntake.ps1`
- Repo-local Codex handoff skill: `.agents/skills/uaix-handoff/`
- Thin coding-agent pointers: `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, `.github/copilot-instructions.md`
## Package Output
- Publish destination: `[local path redacted]`
- UAIX produces the experimental `uai1-project-handoff.zip` WordPress package from `wp-content/plugins/uai1-project-handoff/`; sister and evaluation sites such as LlmWikis.org and AIWikis.org should consume the UAIX-published ZIP rather than acting as the canonical source.
- The current Project Handoff plugin scaffold is hardened for LLM Wiki/AIWikis archive consolidation: generated AGENTS.md, readme.human, `.uai/file-handoff.uai`, and `.uai/intake-index.uai` require original report preservation evidence before summaries or staged artifacts count as long-term memory.
- Current package dogfood expectation: generated Project Handoff exports include root `AGENTS.md`, root `readme.human`, the loaded `.uai` files for context, stack, architecture, constraints, decisions, progress, operations, test plan, style, sources, prompts, file handoff, and intake index, plus `agent-file-handoff/Content/`, `agent-file-handoff/Improvement/`, and `agent-file-handoff/Archive/`.
## Public Route Shape
- Public pages use `/en-us/...`
- AI Memory canonical page: `/en-us/ai-memory/`; `/AI_Memory` redirects to it as a non-canonical entry alias.
- AI Memory LLM Wiki guide page: `/en-us/ai-memory/llm-wiki/`; current role is optional package-tailoring guidance for projects that use an LLM Wiki, not a UAI specs or standards requirement.
- Guides index: `/en-us/guides/`.
- Agentic Harness Strategies and UAI guide: `/en-us/guides/agentic-harnesses-uai/`; current role is strategy guidance for keeping runtime harness execution, MCP/A2A coordination, observability traces, and policy controls separate from UAI-owned portable evidence, AI Memory, Project Handoff, conformance material, and support boundaries.
- OpenAI/Codex Project Handoff guide: `/en-us/guides/project-handoff-openai/`; current role is compatibility guidance that keeps OpenAI runtime orchestration separate from UAIX repo-local project memory.
- Coding-agents Project Handoff guide: `/en-us/guides/project-handoff-coding-agents/`; current role is compatibility guidance for sharing one repo-local handoff bundle across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans without claiming official adapters.
- Project Handoff Context Budget guide: `/en-us/guides/project-handoff-context-budget/`; current role is practical maintenance guidance for keeping hot handoff files concise while bulky history moves to AIWikis or LLM Wiki cold memory with transfer evidence.
- AI Memory Package Wizard page: `/en-us/tools/ai-memory-package-wizard/`; current output is a six-step guided flow with direct setup paths for base, Agent File Handoff, LLM Wiki, and combined File Handoff plus LLM Wiki modes; page-level validation; local browser draft restore; sensitive/high-risk review gate auto-enabling; a dedicated review/export step; package model JSON; manifest overlay JSON; generated exact-root `UAI_MEMORY_SYSTEM_PROFILE.md`, `UAI_MEMORY_RECEIVER_BRIEF.md`, `UAI_MEMORY_STARTUP_PACKET.md`, optional generated exact-root `AGENT_FILE_HANDOFF_PLAN.md`, copy-paste file deck, optional generated exact-root `LLM_WIKI_MEMORY_PLAN.md`, LLM Wiki strategy/topology fields, steward/source/evidence-log metadata, a readiness checklist, operating strategy fields for collaboration model, memory architecture, unit/integration testing, test timing, deployment, code review, release gates, source-authority policy, memory-update policy, evidence ledger path, conflict-resolution policy, change-risk level, rollback strategy, advanced audience/sensitivity/review metadata, optimized human and visitor-AI entry artwork, an embedded visitor-AI digest generated from the same wizard payload, and canonical starter ZIP links over supported bundles.
- Enabled translated public pages also resolve through `/zh-cn/...`
- Query-string URLs such as `?page_id=`, `?p=`, and `?s=` are not public launch URLs
## Public Language Scope
- Enabled locales: `en-US`, `zh-CN`
- Disabled inventory locales: `es-US`, `fr-FR`, `spiral`
- Do not treat disabled locales as supported public languages until content, metadata, hreflang, sitemap, and rendered-text audit coverage are complete.
## Handoff Stack Notes
- Root `AGENTS.md` coordinates AI handoff.
- Root `AGENTS.md` is the only canonical agent instruction front door. Do not create `agent.md`, `Agents.md`, or other competing agent-instruction sources; tool-specific compatibility pointers should redirect readers back to `AGENTS.md`.
- Root `readme.human` is the human-facing companion that explains what people need to know from the AI perspective; it is source-only guidance and does not override constraints.
- `.uai/` files carry durable project context beside the repo.
- `.agents/skills/uaix-handoff/` packages the local Codex pickup workflow as a reusable skill so a future Codex session can repeat intake, context loading, and targeted verification without turning the skill into a public support claim.
- `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md` are thin compatibility pointers back to `AGENTS.md`; they must not become separate state, policy, roadmap, or support-claim sources.
- Recurring Codex/agent handoff work uses the specialized local path: load local files, refresh local intake, run local lint, and use direct UAIX.org page reading only for bootstrap or refresh.
- Public guidance currently supports draft Markdown context-profile files and draft JSON information-profile files.
- Project Handoff should be described as a portable project-memory layer for runtimes and coding-agent surfaces such as OpenAI, Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans, not as a runtime orchestrator, scheduler, OpenAI replacement, official vendor adapter, or competing tool-calling framework.
- `agent-file-handoff/Content/` is the source-only bucket for candidate public/editorial material from humans and other AI systems.
- `agent-file-handoff/Improvement/` is the source-only bucket for audits, QA findings, SEO reports, bug notes, roadmap suggestions, and site-fix work.
- `agent-file-handoff/Archive/` is the source-only dead archive for already-dispositioned files. Routine AI intake ignores it unless a human explicitly names an archived file or moves it back into an active bucket.
- Every new AI work session that loads `AGENTS.md` must check both buckets and process new files before broad planning, regardless of whether the human prompt mentions files.
- `scripts/Invoke-UaiFileIntake.ps1` is the local helper for that chat-start intake pass. It lists current dropped files, writes bucket names, route hints, and checksums into `.uai/intake-index.uai`, marks non-executable files as `needs-agent-review`, and does not move or publish files.
- A `needs-agent-review` entry is a required action item, not passive context: inspect the file, summarize it, and disposition it before unrelated broad work continues.
- Watcher scripts, daemons, queue folders, manifests, always-on background services, and bucket-local README instruction files are not part of the base handoff pattern and should be discouraged in public guidance.
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 stack 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 Stack; Runtime; Active Public Surface; Canonical Workspace And External Distribution; Key Content Sources; Release And QA Scripts; Package Output; Public Route Shape. 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-05-03T02:48:13.1276041Z - Source origin:
current-source-workspace - Retrieval method:
local-source-workspace - Duplicate group:
sfg-298(primary) - Historical hash records are stored in
data/hashes/source-file-history.jsonl.
Machine-Readable Metadata
{
"title": "UAIX Stack",
"source_site": "uaix.org",
"source_url": "https://uaix.org/",
"canonical_url": "https://aiwikis.org/uaix/uai-system/files/uai-stack-uai-9cdfe89b/",
"source_reference": ".uai/stack.uai",
"file_type": "uai",
"content_category": "uai-system",
"content_hash": "sha256:9cdfe89bdd0027f06c79bdc71febf3180532c298b32ba2be6009d9235fd0f05c",
"last_fetched": "2026-05-03T02:48:13.1276041Z",
"last_changed": "2026-05-02T23:56:15.5776608Z",
"import_status": "unchanged",
"duplicate_group_id": "sfg-298",
"duplicate_role": "primary",
"related_files": [
],
"generated_explanation": true,
"explanation_last_generated": "2026-05-03T02:48:13.1276041Z"
}