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/files/uai-public-surface-uai-96c3de57/
Source reference	.uai/public-surface.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-21T19:53:44.0744361Z
Content hash	sha256:96c3de573ed949379df1f6a3ff9409cca187be737daf55faa5778cc577329e7c
Import status	changed
Raw source layer	data/sources/uaix/uai-public-surface-uai-96c3de573ed9.uai
Normalized source layer	data/normalized/uaix/uai-public-surface-uai-96c3de573ed9.txt

Current File Content

Structure Preview

• UAIX Public Surface
• Canonical Host And Languages
• Root Discovery Assets
• Primary Public Routes
• Reader Flow
• Current Support Boundaries
• 2026-06-15 Compact Wizard And Mature Project Setup Surface
• Unsupported Until Public Evidence Exists
• Source-Only Materials
• Verification Notes
• 2026-06-11 Public Locale And Package Surface Note
• 2026-06-11 Research Harnesses And Self-Learning Source Note
• 2026-06-11 Active Anchor Setup Continuity Surface
• 2026-06-13 UAIX Talisman Client Public Surface
• 2026-06-13 UAIX v3.105.0 Public Surface Package 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: 49653
• Preview characters: 11772

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: custom
title: "UAIX Public Surface"
created: "2026-04-25"
updated: "2026-06-21"
status: active
author: "UAIX maintainers"
version: 66
---

# UAIX Public Surface

## Canonical Host And Languages

- Canonical host: `https://uaix.org`.
- Public route shape: clean locale-prefixed paths under `/en-us/...`, `/zh-cn/...`, `/fr-fr/...`, and `/es-es/...`.
- Enabled public languages: `en-US`, `zh-CN`, `fr-FR`, and `es-ES`.
- Enabled inventory languages: `en-US`, `zh-CN`, `fr-FR`, and `es-ES`; `spiral` remains disabled 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.
- UAIX.org is the UAI-1 public standards surface and owns the official UAIX .NET package guidance. Current UAIX public routing documents `/en-us/implementations/dotnet-nuget/` for the UAIX-owned `UAIX.UAI`, `UAIX.UAI.Abstractions`, `UAIX.UAI.Memory`, `UAIX.UAI.Build`, `UAIX.AdaptiveInteroperability`, `UAIX.Talisman.AgentClient`, and `UAIX.Talisman.EcosystemManager` NuGet package set. Do not claim a NuGet.org version is published until NuGet.org lists that exact version.
- UAIX persona-transfer public guidance promises source-persona preservation for persona, assistant-profile, companion, AI friend, AI character, and bounded personality packages. The `.uaix` package-format page, `uaix.persona.v1` schema/example, AI Memory Package Wizard generated Totem/Taboo/assistant-profile text, and local UAIX Totem/Taboo anchors now require preserving voice, values, tastes, boundaries, memories, relationship posture, style, selected personality, and continuity as-is, with platform/runtime/legal/safety constraints disclosed outside the persona source.
- `advanced_persona_profile` is a `.uaix` persona-bearing scope for compact `.uai/persona.uai`, detailed `.uai/personality/*.uai` files, and `.uai/evidence/*.uai` source/variance/provenance files. UAIX records package integrity and runtime variance; it does not promise exact cross-platform cloning, platform-policy bypass, system-message override, hosted import, certification, endorsement, SDK/CLI, runtime execution, or live publication without evidence.
- `/en-us/governance/cognitive-liberty-charter/` is the sole canonical public UAIX Cognitive Liberty Charter Draft route. Older Mission and Principles cognitive-liberty language is context and traceability, not an alternate charter version.
- `/AI_Memory` is a non-canonical requested entry alias that redirects to `/en-us/ai-memory/`.
- Long-form/public-request aliases now redirect to canonical records: `/en-us/implementations/wordpress-publication-track/` -> `/en-us/implementations/wordpress-reference/`, `/en-us/implementations/dotnet-bridge-track/` -> `/en-us/implementations/dotnet-bridge/`, `/en-us/specification/agents-md-uai-linking-specification/` -> `/en-us/specification/agents-md/`, and `/en-us/guides/agent-file-handoff/` -> `/en-us/specification/agent-file-handoff/`.

## Root Discovery Assets

- `/robots.txt`
- `/sitemap.xml`
- `/sitemap.html`
- `/.well-known/uaix.json`
- `/.well-known/uai.json`
- `/.well-known/ai-agent.json`
- `/.well-known/openapi.json`
- `/schemas/index.json`
- `/examples/index.json`
- `/spec/ai-ready-web-requirements.json`
- `/spec/ai-ready-web-maturity-register.json`
- `/spec/ai-ready-web-route-inventory.json`
- `/spec/ai-ready-web-manifest.schema.json`
- `/spec/ai-ready-web-manifest.example.json`
- `/spec/ai-ready-web-readiness-result.schema.json`
- `/spec/ai-ready-web-readiness-result.example.json`
- Root well-known records carry bounded trust metadata pointers to `/wp-json/uaix/v1/trust-channels`, preserving the six-field compact trust prefix plus descriptive tail fields not required for compact trust readers without claiming hosted credential validation, certification, endorsement, runtime enforcement, or a mandatory credential stack.

## Primary Public Routes

Orientation and memory:

- `/en-us/`
- `/en-us/get-started/`
- `/en-us/ai-ready-web/`
- `/en-us/ai-ready-web/executive-audit/`
- `/en-us/ai-ready-web/architecture/`
- `/en-us/ai-ready-web/specification/`
- `/en-us/ai-ready-web/implementation/`
- `/en-us/ai-ready-web/schemas-examples/`
- `/en-us/ai-ready-web/validator-testing/`
- `/en-us/ai-ready-web/roadmap-governance/`
- `/en-us/ai-memory/`
- `/en-us/ai-memory/canonical-ai-memory/`
- `/en-us/ai-memory/llm-wiki/`
- `/en-us/ai-memory/uai-files/`
- `/en-us/ai-memory/uai-files/memory-maintenance-uai/`
- `/en-us/ai-memory/uai-files/next-recursive-prompt-uai/`
- `/en-us/ai-memory/talisman-system/`
- `/en-us/ai-memory/uaix-package-format/`
- `/en-us/ai-memory/uai-files/persona-uai/`
- `/en-us/ai-memory/uai-files/persona-uai/personality-packs/`
- `/en-us/guides/agent-communication-operating-model/`
- `/en-us/tools/ai-memory-package-wizard/`
- `/en-us/standards/`
- `/en-us/standards/uai-1/`
- `/en-us/standards/spec-01/`
- `/en-us/standards/spec-02-project-handoff/`
- `/en-us/standards/spec-03-agents-md/`
- `/en-us/standards/spec-04-file-handoff/`
- `/en-us/standards/capability-ladder/`
- `/en-us/standards/low-capability-agents/`
- `/en-us/standards/advanced-agents/`

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/long-running-goal-execution/`
- `/en-us/guides/hierarchical-goal-memory/`
- `/en-us/guides/project-handoff-coding-agents/`
- `/en-us/guides/project-handoff-context-budget/`
- `/en-us/guides/project-handoff-knowledge-graphs/`
- `/en-us/guides/capability-adaptive-web-interaction/`
- `/en-us/guides/limited-browser-support/`
- `/en-us/guides/advanced-agent-support/`
- `/en-us/guides/browser-and-agent-parity/`
- `/en-us/guides/uaix-vs-mcp-vs-webhooks/`
- `/en-us/guides/agent-consent-boundaries/`
- `/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/`
- `/en-us/registry/uai-agent-message-v1/`
- `/en-us/registry/uai-agent-ack-v1/`
- `/en-us/registry/uai-agent-task-status-v1/`
- `/en-us/registry/uai-agent-blocker-v1/`
- `/en-us/registry/uai-agent-memory-proposal-v1/`
- `/en-us/registry/uai-agent-handoff-v1/`
- `/en-us/registry/uai-agent-final-report-v1/`
- `/en-us/registry/uai-agent-correction-v1/`

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/`
- `/en-us/governance/principles/`
- `/en-us/governance/cognitive-liberty-charter/`
- `/en-us/governance/principles-role-guidance/`
- `/en-us/governance/policy-and-security/`
- `/en-us/governance/privacy-and-data/`
- `/en-us/governance/accessibility/`
- `/en-us/governance/analytics/`
- `/en-us/governance/launch-readiness/`
- `/en-us/governance/changelog/`
- `/en-us/about/related-links/`

Implementation tracks:

- `/en-us/implementations/`
- `/en-us/implementations/wordpress-reference/`
- `/en-us/implementations/dotnet-bridge/`
- `/en-us/implementations/dotnet-nuget/`
- `/en-us/implementations/wordpress-publication-track/` (alias)
- `/en-us/implementations/dotnet-bridge-track/` (alias)

## 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, derived 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 Agent Communication Operating Model when multi-agent work needs portable identity, intent, context refs, acknowledgement, task status, blocker, memory proposal, validation evidence, correction, final report, and handoff records without making UAIX the runtime.
6. Use Standards when a receiver needs the normative publication envelope, Project Handoff, AGENTS.md, File Handoff, capability-ladder, low-capability, or advanced-agent rules in one route family.
7. Use Capability-Adaptive Web Interaction when a public record must tell crawlers, structured fetchers, browser-assisted agents, tool callers, workflow agents, multi-agent runtimes, or audited systems what they can safely do, what fallback applies, what consent is required, and what evidence must travel.
8. Use Project Handoff when the task is repository-local transfer through root `AGENTS.md`, `.uai/readme.human`, and `.uai` files.
9. Use the OpenAI/Codex guide when runtime-orchestration confusion is likely.
10. 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.
11. 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.
12. 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.
13. 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.
14. Use Hierarchical Goal Memory when long-running work needs explicit subgoals, Folded Records, Derived Memory Hierarchies, Bounded Evidence Retrieval, Context Packs, Fresh-Context Review, and Review-Gated Promotion while reviewed source files remain authoritative.
15. 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, graph-assisted retrieval boundaries, and reviewed promotion rules.
16. 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.
17. The Talisman System page now has two roles: default guidance that `.uai/totem.uai`, `.uai/taboo.uai`, and `.uai/talisman.uai` are universal active instruction files to read and obey by default, and advanced guidance for local external enforcement, no-op talk-back, human review, audit evidence, and rollback when a complicated ecosystem needs anchor change-control. UAIX records guidance and evidence boundaries only; local runtime/repository systems own enforcement.
18. Use reports for proposal history and deeper rationale.
19. Use UAI-1, schemas, registry, examples, validator, Adoption Kit, and Conformance Pack when local memory becomes public exchange or reusable evidence.

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; 2026-06-15 Compact Wizard And Mature Project Setup Surface; Unsupported Until Public Evidence Exists. 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
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-723 (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/files/uai-public-surface-uai-96c3de57/",
    "source_reference":  ".uai/public-surface.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:96c3de573ed949379df1f6a3ff9409cca187be737daf55faa5778cc577329e7c",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-21T19:53:44.0744361Z",
    "import_status":  "changed",
    "duplicate_group_id":  "sfg-723",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}