UAIX Public Surface

Orientation and memory:

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/uai-system/files/uai-public-surface-uai-198002f1/
Source reference	.uai/public-surface.uai
File type	uai
Content category	uai-system
Last fetched	2026-05-08T21:22:18.3035107Z
Last changed	2026-05-06T23:10:29.8437033Z
Content hash	sha256:198002f1389d9389dc01ea9cf6e8bf35e94d101d158269362402bee5ad418daa
Import status	unchanged
Raw source layer	data/sources/uaix/uai-public-surface-uai-198002f1389d.uai
Normalized source layer	data/normalized/uaix/uai-public-surface-uai-198002f1389d.txt

Current File Content

Structure Preview

• UAIX Public Surface
• Canonical Host And Languages
• Root Discovery Assets
• Primary Public Routes
• Reader Flow
• Current Support Boundaries
• Unsupported Until Public Evidence Exists
• Source-Only Materials
• Verification Notes

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 12441
• Preview characters: 11964

---
uaix: "1.0"
type: custom
title: "UAIX Public Surface"
created: "2026-04-25"
updated: "2026-05-06"
status: active
author: "UAIX maintainers"
version: 45
---

# UAIX Public Surface

## Canonical Host And Languages

- Canonical host: `https://uaix.org`.
- Public route shape: clean locale-prefixed paths under `/en-us/...` and `/zh-cn/...`.
- Enabled public languages: `en-US` and `zh-CN`.
- Disabled inventory languages: `es-US`, `fr-FR`, and `spiral`; do not treat them as supported until content, metadata, hreflang, sitemap, and rendered-text audits ship together.
- `uiax.org` and `www.uiax.org` are typo-domain aliases for anonymous public traffic and should redirect to `https://uaix.org` with path/query preserved. Do not redirect typo-domain `/wp-admin/`, `/wp-login.php`, or logged-in sessions away from the typo host.
- Protocol5.com is not a UAI-1 public standards surface. It may distribute .NET/NuGet implementation artifacts and backlink to UAIX.org.
- `/AI_Memory` is a non-canonical requested entry alias that redirects to `/en-us/ai-memory/`.

## Root Discovery Assets

- `/robots.txt`
- `/sitemap.xml`
- `/sitemap.html`
- `/.well-known/uaix.json`
- `/.well-known/uai.json`

## Primary Public Routes

Orientation and memory:

- `/en-us/`
- `/en-us/get-started/`
- `/en-us/ai-memory/`
- `/en-us/ai-memory/canonical-ai-memory/`
- `/en-us/ai-memory/llm-wiki/`
- `/en-us/tools/ai-memory-package-wizard/`

Project Handoff and agent guidance:

- `/en-us/specification/project-handoff/`
- `/en-us/guides/agentic-harnesses-uai/`
- `/en-us/guides/uaix-uai-1-agent-skill/`
- `/en-us/guides/project-handoff-openai/`
- `/en-us/guides/project-handoff-coding-agents/`
- `/en-us/guides/project-handoff-context-budget/`
- `/en-us/guides/project-handoff-knowledge-graphs/`
- `/en-us/specification/agent-file-handoff/`
- `/en-us/specification/agents-md/`
- `/en-us/reports/`
- `/en-us/reports/relationship-audit-aiwikis-llmwikis-uaix/`
- `/en-us/reports/llm-wiki-vs-uaix-project-handoff/`
- `/en-us/reports/llm-wiki-and-uaix-project-handoff/`
- `/en-us/reports/refining-uai-protocol-agent-communication/`

UAI-1 contract and evidence:

- `/en-us/specification/uai-1/`
- `/en-us/specification/standards-fit/`
- `/en-us/schemas/`
- `/en-us/registry/`
- `/en-us/examples/`
- `/en-us/tools/api-reference/`
- `/en-us/tools/validator/`
- `/en-us/tools/adoption-kit/`
- `/en-us/tools/conformance-pack/`
- `/en-us/tools/uaix-agents-protocol/`
- `/en-us/roadmap/`
- `/en-us/governance/changelog/`
- `/en-us/about/related-links/`

## Reader Flow

1. Start at Get Started.
2. Use AI Memory for durable AI project-context framing and supported starter bundles.
3. Use Canonical AI Memory when deciding which layer owns source preservation, durable wiki memory, optional graph projections, compact operating packets, transfer context, runtime execution, and the infrastructure choice between short-term memory, long-term memory, and integrated orchestration.
4. Use the Package Wizard to plan one supported memory starter into generated local files and exports; humans use the visible wizard controls, while visiting AI agents read the embedded digest generated from the same wizard payload.
5. Use Project Handoff when the task is repository-local transfer through `AGENTS.md`, `readme.human`, and `.uai` files.
6. Use the OpenAI/Codex guide when runtime-orchestration confusion is likely.
7. Use the Agentic Harness Strategies and UAI guide when readers need the layer split: 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.
8. Use the UAIX / UAI-1 Agent Skill Bundle guide when a skills-compatible agent needs the reference bundle for reusable procedures around creating, validating, citing, packaging, and handing off UAI-1 evidence.
9. Use the coding-agents guide when one local bundle must work across Codex, Claude Code, Cursor, Copilot, Gemini Code Assist, local agents, vendors, and humans.
10. Use the Project Handoff Context Budget guide when hot handoff files are accumulating old reports, chat history, roadmap background, or pre-slim snapshots that should move to cold memory with transfer evidence.
11. Use the Project Handoff Knowledge Graphs guide when a team wants graph-ready handoff memory, stable IDs, claim/evidence states, derived JSON-LD/RDF or property-graph projections, GraphRAG boundaries, and reviewed promotion rules.
12. Use Agent File Handoff when dropped files must be reviewed, dispositioned, understood in relation to the current prompt, preserved in the right hot/cold memory layer, and converted into actual project work during chat-start or prompt-coupled intake.
13. Use reports for proposal history and deeper rationale.
14. Use UAI-1, schemas, registry, examples, validator, Adoption Kit, and Conformance Pack when local memory becomes public exchange or reusable evidence.
15. Use Guides and Standards Fit when explaining agentic systems: runtime harnesses execute, MCP connects tools, A2A coordinates agents, observability traces behavior, and UAIX preserves the portable evidence and handoff record.
16. Use Reports as source leads only after checking whether a conclusion was promoted into current pages, machine artifacts, tests, changelog entries, roadmap state, or handoff records.
17. Use Roadmap and Changelog before making current-support or future-tooling claims.
18. Use the Roadmap today-focus path, roadmap work documentation ledger, work queue, evidence promotion gates, and support-claim checks before moving reader-orientation, first-proof, AI Memory package, source-lead promotion, future-agent pickup, agentic-system evidence, deployment, wizard serializer parity, local validation, redaction lint, trace-to-handoff, reference-adapter, capability-package sidecar, SDK, CLI, certification, endorsement, conformance, or sync ideas into current support language.

## Current Support Boundaries

- Canonical AI Memory is current as bounded public guidance for raw sources, reviewed LLM Wiki memory, optional derived graph projections, compact UAI AI Memory packets, Project Handoff transfer context, execution agents, and public infrastructure comparison between short-term memory, long-term memory, and integrated orchestration. It is not a hosted memory service, hosted graph service, automatic sync path, SDK, CLI, certification, endorsement, official adapter, or conformance profile.
- AI Memory starter ZIPs and the Package Wizard are current as canonical bundle-registry outputs, local planning UI, direct setup URL fragments for base, Agent File Handoff, LLM Wiki, and combined paths, Canonical AI Memory links, optimized human/visitor-AI entry artwork, embedded visitor-AI digest JSON, generated local files including optional `AGENT_FILE_HANDOFF_PLAN.md` and `LLM_WIKI_MEMORY_PLAN.md`, optional LLM Wiki knowledge graph strategy/stable-ID/claim-provenance/validation/retrieval/export-boundary planning, project-scope choices for Proof of Concept, Maintenance of Legacy System, and Greenfield Enterprise Software, workspace coordinator path/root/AGENTS.md verification for multisite setup, prompt-coupled active intake refresh, preference-preserving memory reorganization guidance, JSON exports, copyable decks, readiness metadata, release-bound before/after hot-memory size reporting guidance, and canonical starter downloads. The plain wizard route defaults to Base setup. LLM Wiki setup asks for or discovers the wiki root URL/repository path, index, log/evidence path, coding-standards path, promotion owner, and any graph-readiness policies before using wiki memory; base and File Handoff setup do not force that question.
- Project Handoff is portable project memory for humans and AI agents, not a runtime, scheduler, orchestrator, OpenAI replacement, tool-calling framework, or official vendor adapter.
- Project Handoff Knowledge Graphs is current as public guidance for graph-ready handoff design, derived read-only graph projections, stable IDs, claim/evidence states, graph lint, and GraphRAG boundaries. It is not a hosted graph database, public graph API, public SPARQL endpoint, automatic import, automatic LLM Wiki sync, SDK, CLI, certification, endorsement, conformance profile, or official adapter.
- Capability-package sidecars and mapping annexes are research-track evidence-mapping ideas only. They may inform future optional mappings for skill folders, plugin manifests, action groups, agent cards, MCP/OpenAPI capability surfaces, declarative-agent manifests, and subagent profiles; they are not a current package profile, registry, authorization layer, official adapter, SDK, CLI, certification, endorsement, or conformance support claim.
- LLM Wiki guidance is optional package-tailoring support for projects that already use or deliberately choose deeper wiki memory; it is not required by UAI specs or standards. The guide should stay aligned with LLMWikis.org's build guidance: preserve raw sources, compile reviewed wiki pages, maintain index/log navigation, use metadata and trust labels, review ingest before writing durable memory, keep retrieval behind curated sources, and promote only reviewed facts into compact UAI packages or current project truth.
- Agent File Handoff is chat-start and prompt-coupled intake plus reviewed work, not CI pickup, a queue, a watcher, a daemon, a background service, or automatic publication. Current public guidance requires a live refresh when the newest prompt names active intake or likely relates to active drops, then a complete intake outcome for safe relevant files: reviewed summary/disposition, hot-memory update or no-change reason, long-memory/archive preservation when configured or `not configured`, and actual project work completed. Memory distribution without project work and workless deferral of a safe relevant report are File Handoff failures.
- The UAIX / UAI-1 Agent Skill bundle is current as a downloadable reference procedure bundle for skills-compatible agents on `/en-us/guides/uaix-uai-1-agent-skill/`. It teaches create, validate, cite, package, and handoff workflows over UAIX's public UAI-1 specification, validator, API routes, Adoption Kit, Conformance Pack, AI Memory, and Project Handoff records. It is not an agent runtime, SDK, CLI, official adapter, certification, endorsement, hosted importer, automatic repository writer, automatic LLM Wiki sync path, capability-package profile, registry, authorization layer, or conformance profile.
- Reports are permanent source/proposal history and role-boundary context, not automatic current support evidence.
- Related Links is external context, not UAIX endorsement, certification, implementation support, or canonical authority.
- Public machine JSON routes are discovery or execution surfaces; human docs remain the indexable citation surfaces.

## Unsupported Until Public Evidence Exists

Do not claim hosted `.uai` upload/import validation, automatic repository writes, automatic LLM Wiki sync, current capability-package profiles or registries, package authorization support, SDK, CLI, certification, endorsement, official vendor adapters, OpenAI adapter support, trace-to-handoff exporter support, WordPress admin package installation, IOTA/JustAnIota/ɩ≃1 protocol or converter support, or validator-backed conformance for repo-local `AGENTS.md`, `readme.human`, `.uai`, or AIWikis archive copies.

## Source-Only Materials

- Repository Markdown, `.uai`, `readme.human`, active intake files, archive files, and slimmed source-note stubs are internal source guidance. They are not public sitemap/discovery payloads or WordPress upload-package content unless deliberately rewritten as public pages.
- AIWikis cold-memory copies and the 2026-05-01 UAIX internal memory reorganization manifest are provenance. They do not change UAIX.org authority and should not widen public support claims.

## Verification Notes

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 custom 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 Public Surface; Canonical Host And Languages; Root Discovery Assets; Primary Public Routes; Reader Flow; Current Support Boundaries; Unsupported Until Public Evidence Exists; Source-Only Materials. 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-08T21:22:18.3035107Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-073 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Public Surface",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/uai-system/files/uai-public-surface-uai-198002f1/",
    "source_reference":  ".uai/public-surface.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:198002f1389d9389dc01ea9cf6e8bf35e94d101d158269362402bee5ad418daa",
    "last_fetched":  "2026-05-08T21:22:18.3035107Z",
    "last_changed":  "2026-05-06T23:10:29.8437033Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-073",
    "duplicate_role":  "primary",
    "related_files":  [

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