UAIX Workspace

Updated: 2026-05-02

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/uai-system/files/readme-md-45e90aad/
Source reference	README.md
File type	md
Content category	memory-file
Last fetched	2026-05-03T02:48:13.1276041Z
Last changed	2026-05-02T19:38:07.6493555Z
Content hash	sha256:45e90aadc3ce079840d02a3c1012b894d9f95811624f88926243e045caa67d4f
Import status	unchanged
Raw source layer	data/sources/uaix/readme-md-45e90aadc3ce.md
Normalized source layer	data/normalized/uaix/readme-md-45e90aadc3ce.txt

Current File Content

Structure Preview

• UAIX Workspace
• Status
• Purpose
• AI Quick Start
• Public UAI Reading Path
• Progressive Navigation
• Current Project Truth
• Canonical Docs
• Background And Helper Docs
• Do Not Load By Default
• Repo Map
• Markdown Conventions
• Scope Note

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 Workspace

Updated: 2026-05-02

## Status

This is the canonical human-and-AI repo overview.

## Purpose

This repository contains the local WordPress Studio workspace for UAIX.org.

Use this file as the human-and-AI onboarding entry point for the repo.

UAI public-site and handoff work has moved out of `[local path redacted]`. Use `[local path redacted]` as the canonical local workspace for UAI-1 public materials.

## AI Quick Start

Read these files in this order:

1. `AGENTS.md`
2. `readme.human`
3. every file listed in the `Loaded Context` section of `AGENTS.md`
4. `.agents/skills/uaix-handoff/` when using Codex and the task touches the handoff bundle or file intake
5. `STUDIO.md` when the work touches WordPress Studio, WP-CLI, packaging, or runtime verification
6. `docs/current-reference.md`
7. `docs/deploy.md`
8. `docs/Mission and Site Plan for UAIX.md`
9. `docs/roadmap.md`
10. `docs/uaix-terminology.md`

Large historical research and proposal files were moved to AIWikis long-term memory on 2026-05-01. Use local stubs and compiled AIWikis nodes for routing, and open raw archived source only when original wording or older provenance is actually needed.

After loading `AGENTS.md`, `readme.human`, and the `.uai` bundle, a new AI should summarize the project in 3-5 bullets and confirm the hard constraints before making a broad change.

Before broad edits, the new AI should also name the files, routes, or docs it expects to touch and the checks it expects to run. If required `.uai` context is missing or contradictory, it should report that blocker before editing.

## Public UAI Reading Path

When the task is about explaining UAI to another AI, team, or implementer, use the public pages in this order:

1. `/en-us/ai-memory/` for the broad AI Memory standard, supported starter configuration chooser, LLM Wiki boundary, and dynamic canonical-template downloads.
2. `/en-us/tools/ai-memory-package-wizard/` for guided package planning over supported starter bundles, package model JSON, manifest overlay JSON, copy-paste files, optional exact-root LLM Wiki plan files, readiness metadata, and canonical ZIP links.
3. `/en-us/specification/project-handoff/` for the practical transfer subtype built from `AGENTS.md`, `readme.human`, and `.uai`; it is portable project memory, not an agent runtime.
4. `/en-us/guides/project-handoff-openai/` when the workflow uses OpenAI Agents, Codex, Skills, MCP, sessions, traces, approvals, or runtime handoffs and the reader needs the complementary boundary.
5. `/en-us/guides/agentic-harnesses-uai/` when the reader needs to separate agentic harness execution strategy from UAI evidence, AI Memory, Project Handoff, conformance, and support-claim boundaries.
6. `/en-us/guides/project-handoff-coding-agents/` when one repo-local handoff bundle needs to work across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans without creating official adapter claims.
7. `/en-us/guides/project-handoff-context-budget/` when handoff files are accumulating old reports, chat history, roadmap detail, or pre-slim snapshots that should move to cold memory with transfer evidence.
8. `/en-us/specification/agent-file-handoff/` for chat-start dropped-file intake and review boundaries.
9. `/en-us/specification/agents-md/` for deeper `.uai` linking and record-shape details.
10. `/en-us/reports/`, `/en-us/reports/llm-wiki-vs-uaix-project-handoff/`, `/en-us/reports/llm-wiki-and-uaix-project-handoff/`, and `/en-us/reports/refining-uai-protocol-agent-communication/` for the public report trail.
11. `/en-us/specification/uai-1/`, `/en-us/schemas/`, `/en-us/registry/`, and `/en-us/examples/` for the current UAI-1 contract.
12. `/en-us/tools/validator/`, `/en-us/tools/adoption-kit/`, and `/en-us/tools/conformance-pack/` when the work needs evidence that can travel.
13. `/en-us/roadmap/` and `/en-us/governance/changelog/` before making current-support or future-tooling claims; the roadmap now carries a today-focus path, roadmap work documentation ledger, current work queue, evidence promotion gates, and support-claim checks for moving future work into support.

## Progressive Navigation

If you do not need the full doc stack up front, use `docs/navigation/README.md` for topic-based traversal.

That helper layer points back to `AGENTS.md`, `README.md`, and `docs/current-reference.md` so readers can move through one topic at a time without losing the canonical entry points.

## Current Project Truth

- This is a local WordPress Studio site.
- UAIX.org is the public standards and publication site for UAI and the source of truth for UAI-1.
- Protocol5.com is not the UAI-1 site; it may distribute .NET plugins and NuGet packages and should link back to UAIX.org for the canonical specification, schemas, registry, validator, roadmap, governance, and support boundaries.
- AIWikis.org is the dogfood implementation and cold-memory archive for large UAIX source notes and processed handoff material. It does not replace UAIX.org as UAI-1 authority or public support evidence.
- The active public theme is `uaix-authority-theme`.
- `uaix-theme` is still packaged and smoke-tested as installable, but it is not the current public launch surface.
- The public site uses clean, descriptive, locale-prefixed paths under `/en-us/...`.
- The enabled public language surface is `en-US` and `zh-CN`; other locale inventory records are disabled until content, hreflang, sitemap, and rendered-text audits are ready.
- Query-string URLs such as `?page_id=`, `?p=`, and `?s=` are not public launch URLs.
- Root `robots.txt`, `sitemap.xml`, `sitemap.html`, `/.well-known/uaix.json`, and `/.well-known/uai.json` are part of the public SEO and discovery surface.
- UAI-1 currently publishes six profiles plus field registry, transport bindings, trust channels, error registry, conformance levels, API Reference, Adoption Kit, live mock exchange, OpenAPI, Conformance Pack, implementation evidence checklist, conformance fixture pack with canonical-hash equivalence and current-boundary negative cases, plus a bridge evidence pack for A2A, MCP, OpenAPI, DID/VC, and Trace Context mappings, public Roadmap, Contact and Review, Standards Fit, schemas, registry, examples, validator normalization for keyed/minified-keyed/keyless JSON, and implementation tracks.
- The public Roadmap and `/wp-json/uaix/v1/roadmap` now include the today-focus path, roadmap work documentation ledger, current work queue, evidence promotion gates, and support-claim checks for reader orientation, first proof runs, AI Memory package work, future-agent pickup, source-lead promotion, agentic-system evidence planning, deployment cleanup, wizard serializer parity, local validation/redaction lint, trace-to-handoff fixtures, reference-adapter evaluation, AI Memory package scope, adapter/runtime scope, and conformance wording.
- The specification surface includes `/en-us/specification/project-handoff/` for portable project memory, governance, and review context built from `AGENTS.md`, `readme.human`, and `.uai` files. It is meant to be consumed by OpenAI, Codex, Claude, local agents, vendors, human teams, and future sessions, but it is not an agent runtime, scheduler, orchestrator, or OpenAI replacement.
- The guides surface includes `/en-us/guides/project-handoff-openai/` for using Project Handoff with OpenAI Agents and Codex. The governing line is: OpenAI runs the agents; Project Handoff preserves the project memory.
- The guides surface includes `/en-us/guides/agentic-harnesses-uai/` for agentic harness strategy and UAI fit. Harnesses execute, MCP/A2A/runtime tools coordinate and trace behavior, and UAI preserves reviewed portable evidence, AI Memory, Project Handoff, conformance material, and support boundaries.
- The guides surface also includes `/en-us/guides/project-handoff-coding-agents/` for thin pointer patterns across Codex, Claude Code, Cursor, GitHub Copilot, Gemini Code Assist, local agents, vendors, and humans. It is compatibility guidance, not official adapter, SDK, CLI, certification, conformance, or endorsement support.
- The guides surface also includes `/en-us/guides/project-handoff-context-budget/` for keeping `AGENTS.md`, `readme.human`, and `.uai` files compact while bulky research, old reports, and pre-slim snapshots move to AIWikis or LLM Wiki cold memory with transfer evidence.
- The public launch surface includes `/en-us/ai-memory/` with `/AI_Memory` as a non-canonical entry alias, `/en-us/tools/ai-memory-package-wizard/`, `/en-us/specification/agents-md/`, `/en-us/reports/`, `/en-us/reports/llm-wiki-vs-uaix-project-handoff/`, `/en-us/reports/llm-wiki-and-uaix-project-handoff/`, and `/en-us/reports/refining-uai-protocol-agent-communication/` for AI Memory framing, guided package planning, the adopted AGENTS.md `.uai` linking proposal, LLM Wiki comparison material, and permanent report trail.
- AI Memory is the broad public/search entry point for durable, portable, human-readable AI project context. Current starter configurations are Project AI Memory, Project Handoff, Agent Session Memory, Onboarding Memory, Decision Memory, Client or Vendor Handoff Memory, Incident or Audit Memory, and LLM Wiki Export Memory, all generated from canonical templates and deterministic manifests. The AI Memory Package Wizard adds a six-step package-planning flow with page-level validation, local browser draft restore, package model JSON, manifest overlay JSON, generated system profile, receiver brief, startup packet, copy-paste file decks, optional exact-root `LLM_WIKI_MEMORY_PLAN.md` files with steward/source/evidence metadata, readiness checks, advanced audience/sensitivity/review metadata, and canonical ZIP links over those same supported starters. Team Memory and Product Memory are views for now. Project Handoff is the transfer subtype for `AGENTS.md`, `readme.human`, and `.uai`; the LLM Wiki reports, AGENTS.md specification, and refining report are deeper reference material.
- Governance currently includes dedicated pages for policy and security, privacy and data, accessibility, analytics, launch readiness, and changelog.
- Release QA currently includes launch-surface, machine-route, response-header, zh-CN translation, package-validation, and Studio smoke-test checks through the scripted publish path.
- There is no pre-launch obligation to preserve legacy aliases such as `/spec/` or historical Protocol5 paths. Protocol5.com should be treated as an external .NET/NuGet distribution and backlink surface, not as a UAIX launch route or UAI-1 authority.

## Canonical Docs

- `docs/current-reference.md` is the short source-of-truth index.
- `docs/deploy.md` is the canonical deployment, routing, and release reference.
- `docs/Mission and Site Plan for UAIX.md` is the canonical plan for public positioning, IA, and launch-surface ownership.
- `docs/roadmap.md` is the canonical future roadmap.
- `docs/uaix-terminology.md` is the canonical naming reference.
- `docs/UAIX-spec.md` is now a slim source stub. Use `/en-us/specification/project-handoff/`, `.uai/handoff-pattern.uai`, and root `AGENTS.md` for current Project Handoff behavior; use AIWikis long memory only for the original draft wording.
- root `readme.human` is the human-facing briefing from the AI perspective; it helps people know what to make explicit, but it does not override `AGENTS.md`, `.uai/constraints.uai`, system instructions, repo rules, or human requests.
- `.uai/` is the live repository-context bundle used by root `AGENTS.md` for zero-context AI onboarding in this repo.
- `.uai/handoff-pattern.uai` explains how to turn public website instructions, README guidance, release notes, and operating docs into a self-contained `AGENTS.md`, `readme.human`, and `.uai` handoff bundle.
- `.agents/skills/uaix-handoff/` is the repo-local Codex skill that repeats the handoff load, intake review, and targeted-check workflow without becoming a separate source of truth.
- `CLAUDE.md`, `GEMINI.md`, `.cursor/rules/uaix-handoff.mdc`, and `.github/copilot-instructions.md` are thin tool-specific pointers back to `AGENTS.md`; they are not separate project-truth files.
- `docs/UX Accessibility Technical Content and SEO Audit of UAIX.org.md` is the current audit baseline.

## Background And Helper Docs

- Research notes in `docs/` are background inputs, not launch truth.
- Some large research notes in `docs/` are now source stubs that point to AIWikis `raw/system-archives/2026-05-01-uaix-internal-memory-reorg.json`.
- Older dated roadmap files are historical inputs; use `docs/roadmap.md` for open work.
- `docs/uaix_expanded_roadmap.md` and `docs/UAIX_roadmap_and_interoperability_report.md` are slim stubs for cold roadmap source material; use `docs/roadmap.md` for the current plan.
- Compatibility-pointer docs such as `docs/deploy-current.md` and `docs/ns12-locale-routing-deployment.md` should stay short and point back to canonical docs.
- `docs/navigation/` contains helper maps for progressive reading and should always point back to `AGENTS.md`, `README.md`, and `docs/current-reference.md`.
- `docs/navigation/ai-handoff.md` is the helper path for AI Memory, the AI Memory Package Wizard, Project Handoff, root `readme.human`, AGENTS.md-linked `.uai` files, and the report trail.
- Theme local-install markdown files and publish or mirror docs are packaging helpers, not separate policy sources.

## Do Not Load By Default

These repo areas are usually non-primary traversal zones:

- `.tmp/` for temporary artifacts, extracted archives, screenshots, and one-off readbacks
- `wp-content/Publish/` for packaged publish output and mirrored release payloads
- `wp-content/themes/uaix-authority-theme-local-install/` for the local-install mirror of the active theme
- bundled WordPress core or third-party areas unless a task explicitly targets them

## Repo Map

- `wp-content/themes/uaix-authority-theme/` contains the active public theme.
- `wp-content/plugins/` contains UAIX and locale-routing plugins.
- `wp-content/README.md` is the local content-tree entry point.
- `wp-content/plugins/README.md` is the local plugin traversal guide.
- `wp-content/themes/README.md` is the local theme traversal guide.
- `docs/` contains project documentation.
- `docs/navigation/` contains topic-based helper maps for selective reading.
- `scripts/README.md` is the local automation and release-script guide.
- `scripts/` contains packaging, smoke-test, and release automation.

## Markdown Conventions

Project-authored markdown should be easy for both humans and AIs to parse:

- start with a clear top-level title
- include `Updated:` when the file is an active project doc
- state whether the document is canonical, background, or a compatibility pointer
- say how the document should be used
- point to the canonical source if the file is not authoritative
- run `scripts/audit-helper-docs.ps1` after renaming helper docs or changing traversal links
- update canonical docs when project truth changes
- treat Markdown instruction files as source-only guidance, not public site files or WordPress upload payload

## Scope Note

This AI-readability pass applies to project-authored markdown in the repo.

It does not attempt to rewrite third-party upstream files such as WordPress core licenses or bundled vendor documentation.

Why This File Exists

This is a memory-system evidence 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 file is memory-system evidence. It records source history, archive transfer, intake disposition, or another piece of provenance that should be retrievable without becoming an unsupported public claim.

Structure

The file is structured around these visible headings: UAIX Workspace; Status; Purpose; AI Quick Start; Public UAI Reading Path; Progressive Navigation; Current Project Truth; Canonical Docs. 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

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

Provenance And History

• Current observation: 2026-05-03T02:48:13.1276041Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-124 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Workspace",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/uai-system/files/readme-md-45e90aad/",
    "source_reference":  "README.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:45e90aadc3ce079840d02a3c1012b894d9f95811624f88926243e045caa67d4f",
    "last_fetched":  "2026-05-03T02:48:13.1276041Z",
    "last_changed":  "2026-05-02T19:38:07.6493555Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-124",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-05-03T02:48:13.1276041Z"
}