Mission And Site Plan For UAIX

Updated: 2026-04-26

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-docs-mission-a-194efb07/
Source reference	raw/system-archives/uaix/internal-memory-reorg/2026-05-01/docs/Mission and Site Plan for UAIX.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-04-29T02:27:14.4635583Z
Content hash	sha256:194efb0739a5996e3963cfc494cd17b6d604e5e5247072ef71573a1c639d33cf
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-docs-mission-and-site-plan-for-uaix-md-194efb0739a5.md
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-docs-mission-and-site-plan-for-uaix-md-194efb0739a5.txt

Current File Content

Structure Preview

• Mission and Site Plan for UAIX.org
• Status
• Purpose
• How To Use This Document
• Mission
• What UAIX Is
• What UAIX Is Not
• Naming Model
• Standards-Fit Positioning
• Current Launch-Surface Truth
• Current Public Information Architecture
• Launch Posture
• Launch-Surface Ownership
• Delivery Direction
• Trust-Infrastructure Direction
• Priority Roadmap
• Practical Editing Rule

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: 15643
• Preview characters: 11933

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

# Mission and Site Plan for UAIX.org

Updated: 2026-04-26

## Status

This is the canonical mission, information architecture, and launch-surface ownership plan for UAIX.

## Purpose

This document is the current source of truth for UAIX mission, public information architecture, and launch-surface ownership.

Use it when editing site copy, planning public pages, deciding what belongs in the launch surface, or judging whether older planning notes still match the current project direction.

## How To Use This Document

- Use this file for public positioning, route-model, and launch-surface ownership.
- If another markdown file conflicts with this file about the UAIX launch surface, this file wins unless `docs/deploy.md` or `docs/uaix-terminology.md` is more specific.
- Prefer `docs/roadmap.md` for future priorities and for deciding whether older recommendations are still open work.
- Prefer `docs/deploy.md` for deployment procedure, smoke tests, release checks, and environment-level routing validation.
- Prefer `docs/uaix-terminology.md` for naming decisions.

Current companion references:

- `docs/current-reference.md` for the short canonical index
- `docs/roadmap.md` for current future priorities
- `docs/deploy.md` for deployment, routing, and release rules
- `docs/uaix-terminology.md` for naming rules

Selective traversal helpers:

- `docs/navigation/launch-surface.md` when you only need public IA, naming, or launch-posture context
- `docs/navigation/implementation-and-runtime.md` when the question also touches theme, plugin, or runtime ownership

## Mission

UAIX is the public standards and publication surface for UAI.

UAI is the protocol family.
UAI-1 is the current normative specification.

UAIX should present UAI as a serious interoperability, conformance, and publication standard, not as a generic AI blog, a developer dashboard, a plugin storefront, or an account-driven application.

UAI public materials now belong in `[local path redacted]` after the split from `[local path redacted]`. UAIX.org is the source of truth for UAI-1. Protocol5.com is a separate .NET plugin and NuGet package distribution surface that should link back to UAIX.org for the canonical standard.

## What UAIX Is

- a standards-oriented public website
- the publication home for UAI and UAI-1
- the place where readers find the specification, schemas, registry, examples, governance notes, validator guidance, conformance-facing materials, machine-readable discovery manifests, press assets, changelog entries, and reference implementation pages
- a WordPress-based presentation and distribution layer backed by version-controlled canonical artifacts and machine-readable discovery records

## What UAIX Is Not

- not a torrent or media-sharing site
- not a login-first application
- not a marketplace
- not a generic blog with loose technical posts
- not a pre-launch compatibility shell for historical Protocol5 routes
- not Protocol5.com and not a .NET package storefront
- not a replacement for every agent runtime, tool protocol, API description format, identity system, observability system, or binary encoding

## Naming Model

- `UAIX` means the website, publication surface, and standards venue
- `UAI` means the specification family
- `UAI-1` means the current normative release
- `Protocol5.com` means an external .NET plugin and NuGet distribution/linking surface, not the UAI-1 standards site

Do not describe `UAIX` as the protocol version.
Do not use `UAIX v1.0` when the correct reference is `UAI-1`.
Do not describe Protocol5.com as the public site, canonical host, or source of truth for UAI-1.

## Standards-Fit Positioning

UAIX should explain UAI-1 as the public exchange record that can travel across adjacent systems.

Use this plain-language comparison when public copy needs a compact map:

- A2A coordinates agents and long-running peer tasks.
- MCP connects agents or applications to tools, APIs, files, data sources, and workflows.
- OpenAPI describes conventional HTTP APIs.
- JSON Schema validates message structure.
- DID, Verifiable Credential, mTLS, signed-envelope, and related systems can support trust assertions.
- Trace Context and observability systems carry distributed tracing context.
- CBOR, MessagePack, and similar formats can be future compact transport bindings.
- UAI-1 records the portable exchange evidence: identity, intent, workflow state, delivery semantics, trust posture, provenance, integrity, results, errors, and conformance evidence.

Do not imply that UAIX currently replaces these adjacent layers. The public site should show where UAI-1 fits beside them and keep bridge profiles or adapter claims tied to validator-backed evidence.

Bridge-profile language should stay declarative: UAIX can record an A2A Agent Card, an A2A task outcome, an MCP tool call, an OpenAPI operation reference, DID/VC-linked trust evidence, or Trace Context linkage, but the adjacent system still owns its runtime behavior.

## Current Launch-Surface Truth

- The active public theme is `uaix-authority-theme`.
- UAIX.org is the authoritative public source for UAI and UAI-1.
- Protocol5.com may distribute .NET plugins and NuGet packages and should link back to UAIX.org for canonical UAI-1 materials; it is not the UAI-1 launch surface.
- `uaix-theme` is still packaged and smoke-tested as installable, but it is not the current public launch surface.
- Canonical public routes use clean, descriptive, locale-prefixed paths under `/en-us/...`.
- The enabled public language surface is `en-US` and `zh-CN`; disabled locale inventory entries are not public support claims until their full content, metadata, hreflang, sitemap, and rendered-text audits ship together.
- Query-string URLs such as `?page_id=`, `?p=`, and `?s=` are not public launch URLs.
- Root `robots.txt`, `sitemap.xml`, and `sitemap.html` are part of the public SEO surface.
- Root `/.well-known/uaix.json` and `/.well-known/uai.json` are part of the machine-readable discovery surface.
- Machine-readable discovery should remain aligned with the public catalog, API Reference, OpenAPI, validator normalization behavior, mock exchange, adoption kit, conformance pack, implementation evidence checklist, conformance fixture pack, canonical-hash equivalence evidence, roadmap, schema, registry, example, and status routes.
- The current UAI-1 operating surface includes six published profiles, field registry, transport bindings, trust channels, error registry, and conformance levels.
- The public operating surface includes a dedicated Contact and Review page for launch-stage contact, contributor packet, change-proposal, decision-trail, and review-intake guidance.
- The specification surface includes a dedicated Standards Fit page for A2A, MCP, OpenAPI, JSON Schema, DID/VC, Trace Context, compact-transfer, and normalization boundaries. Current validator-supported normalization modes are `keyed-json`, `minified-keyed-json`, and `keyless-json`; the conformance fixture pack now proves canonical-hash equivalence, invalid `traceparent`, DID/VC trust-evidence, required-field, undeclared-field, keyless-shape, keyless-overflow, and unsupported-alias boundaries; alias and binary forms remain future evidence work.
- The public handoff surface includes Project Handoff, the AGENTS.md `.uai` Linking Specification, Reports, and the Refining UAI Protocol for Agent Communication report.
- Governance now includes dedicated child pages for policy and security, privacy and data, accessibility, analytics, launch readiness, and changelog.
- There is no pre-launch obligation to preserve `/spec/`, `/docs/`, or historical Protocol5 paths.

## Current Public Information Architecture

The current public route model is the source of truth for site planning.

- `/en-us/` for the public home and mission
- `/en-us/get-started/` for onboarding
- `/en-us/about/` for institutional framing
- `/en-us/about/references/` for important links, attribution, and contributor guidance
- `/en-us/about/contact-and-review/` for contact, contributor packet, change-proposal, decision-trail, and review-intake guidance
- `/en-us/specification/` for the specification landing page
- `/en-us/specification/uai-1/` for the current normative specification
- `/en-us/specification/standards-fit/` for adjacent-standard fit, current bridge evidence, compact-transfer, future bridge-profile, and normalization boundaries
- `/en-us/specification/project-handoff/` for the practical `AGENTS.md` plus `.uai` project-context handoff pattern
- `/en-us/specification/agents-md/` for deeper AGENTS.md `.uai` linking and record-shape guidance
- `/en-us/schemas/` for schema artifacts
- `/en-us/registry/` for registry records
- `/en-us/examples/` for examples
- `/en-us/implementations/` for implementation tracks
- `/en-us/implementations/wordpress-reference/` for the WordPress reference surface
- `/en-us/implementations/dotnet-bridge/` for the .NET bridge surface
- `/en-us/tools/` for tools
- `/en-us/tools/validator/` for validation
- `/en-us/tools/api-reference/` for machine-facing route documentation and OpenAPI handoff
- `/en-us/tools/adoption-kit/` for the first-proof onboarding bundle
- `/en-us/tools/conformance-pack/` for reusable public conformance evidence, including the implementation evidence checklist
- `/en-us/roadmap/` for the public future-work boundary and interoperability roadmap
- `/en-us/reports/` for the permanent report index and source-note trail
- `/en-us/reports/relationship-audit-aiwikis-llmwikis-uaix/` for the AIWikis, LLMWikis, and UAIX role-boundary audit
- `/en-us/reports/refining-uai-protocol-agent-communication/` for the deeper repository-native UAI handoff report
- `/en-us/governance/` for governance
- `/en-us/governance/changelog/` for changelog records
- `/en-us/governance/policy-and-security/` for policy and security posture
- `/en-us/governance/privacy-and-data/` for privacy and data posture
- `/en-us/governance/accessibility/` for accessibility posture
- `/en-us/governance/analytics/` for analytics posture
- `/en-us/governance/launch-readiness/` for the public go-live gate across response checks, package evidence, accessibility QA, locale QA, release-trail alignment, and support-claim boundaries
- `/en-us/press/` for press assets and public reference language
- `/en-us/news/` for publication news entries

## Launch Posture

Routes and concepts that are no longer planning truth:

- `/spec/uai-1`
- `/implementations/dotnet`
- `/implementations/wordpress`
- `/tools/workbench`
- `/tools/registry`
- `/examples/uai-1`
- bare legacy aliases such as `/spec/`

Protocol5 remains useful as prior art, historical source material, and a future .NET/NuGet distribution surface, but it is not the launch surface or source of truth for UAI-1.

The current launch posture is:

- no pre-launch obligation to preserve old Protocol5 paths
- no deliberate addition of legacy aliases such as `/spec/`
- no internal navigation that depends on bare non-localized paths
- no drift back toward vague or mixed route naming
- no public copy that sends readers to Protocol5.com as the canonical UAI-1 specification, validator, registry, roadmap, or governance authority

If legacy redirects are ever added later, that should be an explicit post-launch decision tied to real inbound demand.

## Launch-Surface Ownership

| Concern | Current owner | Notes |
|---|---|---|
| Public presentation and templates | `wp-content/themes/uaix-authority-theme/` | Active public launch theme. |
| Locale-aware routing | `wp-content/plugins/ns12-locale-router/` | Locale prefixes, request normalization, locale-aware link behavior. |
| Canonical SEO, clean URL enforcement, sitemaps, robots | `wp-content/plugins/uaix-seo-sweep/` | Canonicals, hreflang, JSON-LD, root sitemap and robots generation. |
| Protocol runtime and module registry | `wp-content/plugins/uaix-core/` | Core UAIX REST/runtime ownership. |

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: Mission and Site Plan for UAIX.org; Status; Purpose; How To Use This Document; Mission; What UAIX Is; What UAIX Is Not; Naming Model. 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-121 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "Mission And Site Plan For UAIX",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-internal-memory-reorg-2026-05-01-docs-mission-a-194efb07/",
    "source_reference":  "raw/system-archives/uaix/internal-memory-reorg/2026-05-01/docs/Mission and Site Plan for UAIX.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:194efb0739a5996e3963cfc494cd17b6d604e5e5247072ef71573a1c639d33cf",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-04-29T02:27:14.4635583Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-121",
    "duplicate_role":  "primary",
    "related_files":  [

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