UAIX Roadmap

Updated: 2026-05-02

Metadata

Field	Value
Source site	uaix.org
Source URL	https://uaix.org/
Canonical AIWikis URL	https://aiwikis.org/uaix/files/raw-system-archives-uaix-recent-work-sweep-2026-05-03-docs-roadmap-md-e656937b/
Source reference	raw/system-archives/uaix/recent-work-sweep/2026-05-03/docs/roadmap.md
File type	md
Content category	memory-file
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-05-02T19:39:17.7057324Z
Content hash	sha256:e656937b9413a1f35f07a926f3f3292accb3bfa935296e83ec11018cd072c010
Import status	unchanged
Raw source layer	data/sources/uaix/raw-system-archives-uaix-recent-work-sweep-2026-05-03-docs-roadmap-md-e656937b9413.md
Normalized source layer	data/normalized/uaix/raw-system-archives-uaix-recent-work-sweep-2026-05-03-docs-roadmap-md-e656937b9413.txt

Current File Content

Structure Preview

• UAIX Roadmap
• Status
• How To Use This Document
• No Longer Roadmap Items
• Roadmap Principles
• Today Focus Path
• Roadmap Work Documentation Ledger
• Current Roadmap Work Queue
• Evidence Promotion Gates
• Support Claim Checklist
• Near-Term Priorities
• 1. Production Launch Hardening
• 2. Accessibility And Content QA
• 3. Public Operating Layer
• 4. Standards-Fit And Token-Efficiency Explanation
• 5. Conformance Program Maturity
• 6. Developer Support
• 7. Runtime And Release Architecture
• Medium-Term Priorities
• Longer-Horizon Research Tracks
• Historical Inputs
• Roadmap Metrics

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: 35271
• Preview characters: 11998

# UAIX Roadmap

Updated: 2026-05-02

## Status

This is the canonical forward roadmap for the UAIX workspace.

Use this document for future priorities, roadmap planning, and deciding whether older recommendations are still open work.

## How To Use This Document

- Use this file for current and future roadmap decisions.
- Use `docs/Mission and Site Plan for UAIX.md` for mission, information architecture, and launch-surface ownership.
- Use `docs/deploy.md` for packaging, release, routing, and production validation.
- Use `docs/uaix-terminology.md` for naming.
- Treat older roadmap, audit, and research notes as background unless this document or `docs/current-reference.md` explicitly adopts their recommendations.
- Treat `docs/uaix_expanded_roadmap.md` and `docs/UAIX_roadmap_and_interoperability_report.md` as background idea sources behind the standards-fit, token-efficiency, bridge-evidence, canonicalization, validator-normalization, conformance-fixture, and metrics items adopted here.

## No Longer Roadmap Items

These items are already part of the current public record or release workflow and should not be carried forward as open roadmap work:

- clean locale-prefixed public routes under `/en-us/...`
- the active `uaix-authority-theme` launch surface
- the published UAI-1 specification, schemas, registry, examples, validator, and implementation tracks
- six published profiles: `uai.intent.request.v1`, `uai.intent.response.v1`, `uai.capability.statement.v1`, `uai.error.v1`, `uai.conformance.result.v1`, and `uai.task.status.v1`
- the field registry, transport bindings, trust channels, error registry, and conformance levels
- public pages for API Reference, Adoption Kit, and Conformance Pack
- the expanded public implementation-evidence checklist in the Adoption Kit, Conformance Pack, and discovery surface, including implementation identity, profile scope, validator evidence, machine-route/cache posture, trust and threat boundary, locale/accessibility reader QA, fixtures, release trail, and support boundary
- the public conformance fixture pack in the Adoption Kit, Conformance Pack, discovery surface, and production response-surface checks
- the public bridge evidence pack in the Adoption Kit, Conformance Pack, and discovery surface, with validator-backed A2A Agent Card, A2A task, MCP tool-call, MCP resource-result, OpenAPI operation, DID/VC, and Trace Context mapping examples
- public Roadmap page and machine-readable roadmap route
- public Contact and Review page for launch-stage contact, contributor packet, change-proposal, decision-trail, and review-intake guidance
- public Related Links page for footer-linked outgoing references to adjacent standards, protocol projects, security references, implementation ecosystems, and research resources, with explicit non-endorsement and non-normative boundaries
- public Standards Fit page for A2A, MCP, OpenAPI, JSON Schema, DID/VC, Trace Context, compact-transfer, normalization boundaries, the UAI-1 vs MCP chooser, the UAI-1 vs A2A chooser, and bridge-evidence reading guidance
- public Guides, `/en-us/guides/agentic-harnesses-uai/`, and Standards Fit agentic-system evidence path that explains the runtime/harness versus UAIX split: runtimes execute, MCP connects tools, A2A coordinates agents, observability traces behavior, and UAIX preserves the validator-ready record, conformance packet, AI Memory, and project-memory handoff
- public AI Memory page, `/AI_Memory` redirect alias, supported starter bundle taxonomy generated from canonical templates and visible samples, AI Memory Package Wizard for guided package model JSON, manifest overlay JSON, generated system profiles with source-authority, evidence-ledger, conflict-resolution, risk, and rollback protocols, generated receiver briefs, generated startup packets, copy-paste file decks, optional generated LLM Wiki memory-plan files with steward/source/evidence metadata and readiness checks, and canonical starter ZIP links, Project Handoff page, root `readme.human` briefing convention, Agent File Handoff page, AGENTS.md `.uai` Linking Specification page, Reports index, and Refining UAI Protocol for Agent Communication report as the current public project-context memory, handoff, and dropped-file intake path
- `.uai/test-plan.uai` as the current handoff file for targeted-check policy, package-build triggers, and full-suite release gates
- public Launch Readiness page for the go-live gate across response checks, package evidence, accessibility QA, locale QA, release-trail alignment, and support-claim boundaries
- machine-facing routes for catalog, discovery, schemas, registry, field registry, transport bindings, trust channels, error registry, conformance levels, examples, validation, adoption kit, mock exchange, OpenAPI, conformance pack, roadmap, and status
- machine-route search/cache posture: public UAI REST JSON responses are non-indexable execution surfaces, readable machine routes have explicit short public cache headers, and public POST routes use no-store responses with launch-stage body-size and request-throttle guardrails
- validator normalization for `keyed-json`, `minified-keyed-json`, and `keyless-json`, including field-registry expansion and canonical-hash metadata in the validation result
- reusable positive keyed/minified-keyed/keyless fixture cases, canonical-hash equivalence metadata, and negative missing-profile, missing-required-field, undeclared-field, invalid-traceparent, DID/VC trust-evidence, keyless-shape, keyless-overflow, and unsupported-alias boundary cases in the conformance fixture pack
- keyed `message` and registry-backed `keyless_message` payloads on published example records
- dedicated governance child pages for policy and security, privacy and data, accessibility, analytics, launch readiness, and changelog
- root `robots.txt`, `sitemap.xml`, `sitemap.html`, `/.well-known/uaix.json`, and `/.well-known/uai.json`
- enabled `en-US` and `zh-CN` public language coverage for the current launch surface, with other locale inventory entries disabled until their full content and audits are ready
- homepage standards keywords metadata through the SEO sweep metadata surface
- launch-stage response headers on public WordPress-rendered HTML, HTML sitemap, and REST responses: `X-Content-Type-Options`, `Referrer-Policy`, `Permissions-Policy`, `X-Frame-Options`, `Content-Security-Policy: frame-ancestors 'self'`, and `Strict-Transport-Security` on HTTPS requests
- scripted WordPress package publishing, ZIP validation, fallback production root-asset generation, launch-surface audit with machine-route and response-header checks, zh-CN translation audit, and Studio smoke testing
- the old route-fix work for `Get Started` and `UAI-1`; those routes are no longer treated as broken-news-archive issues

## Roadmap Principles

- Trust infrastructure comes before growth infrastructure.
- Current support claims must stay narrower than the long-term ambition.
- Public pages, machine-readable records, validator evidence, package outputs, and changelog entries should move together.
- Research and strategy reports are source leads until their conclusions are promoted into current docs, public pages, machine artifacts, tests, changelog entries, roadmap state, or handoff records. Keep claim-evidence splits explicit before treating a report as authority.
- Ordinary project work should run targeted checks tied to the changed files, routes, or records; full package/release sweeps belong to ZIP builds, release candidates, broad launch-surface changes, or explicit full-check requests.
- Full build/release work should clean and update internal `.md`, `.uai`, and `.human` source files before package output is treated as current, while keeping those source files out of upload ZIPs and public discovery unless intentionally converted into public copy.
- Chat-start local file intake can refresh `.uai/intake-index.uai` from files dropped directly into `agent-file-handoff/Content/` and `agent-file-handoff/Improvement/`, and any `needs-agent-review` file must be inspected, summarized, and dispositioned before unrelated broad work. Processed files move to `agent-file-handoff/Archive/`, which routine AI intake ignores unless a human explicitly names an archived file or moves it back into an active bucket. AIWikis or another LLM Wiki implementation may consolidate already-dispositioned archive files only by explicit request, with transfer evidence and history/log/index updates before source archive removal. Intake does not publish public content or support claims without review. Watchers, daemons, queue folders, routine pickup manifests, out-of-chat auto-pickup, and bucket-local README instructions are discouraged for the base pattern.
- UAIX.org remains the source of truth for UAI-1; external distribution surfaces such as Protocol5.com should link back instead of becoming competing authorities.
- A2A coordinates agents, MCP connects tools and resources, and UAI-1 records the portable exchange evidence.
- UAIX should stay focused on the portable evidence and handoff layer for agentic systems. Runtime harnesses own model execution, tool access, approvals, tracing, interruptions, orchestration, and managed memory; UAIX records the part that must travel, validate, and survive handoff.
- Bridge profiles should map adjacent-system records into UAI-1 evidence; they should not take over A2A tasks, MCP sessions, identity stacks, tracing stacks, or transport lifecycles.
- The field registry supports compact and keyless transport, while JCS over the fully reconstituted keyed JSON record should remain the integrity and signing baseline.
- Token-efficiency work must be measurable, reversible, validator-backed, and auditable rather than based on hidden or covert machine language.
- Future platform ideas such as gateways, dashboards, settlement, federation, and streaming should remain research tracks until they have public ownership and maintenance capacity.

## Today Focus Path

Use this path before the longer roadmap inventory when the goal is authority and usefulness right now.

1. New readers should start with `/en-us/specification/uai-1/` and `/en-us/specification/standards-fit/`, then use `/en-us/roadmap/` before repeating broad claims about runtime fit, bridge profiles, SDKs, CLIs, adapters, certification, endorsement, or sync.
2. Implementers should produce one useful proof run: choose one public profile, validate one packet, keep the result beside the Adoption Kit or Conformance Pack, and cite the changelog before treating the work as public support.
3. AI Memory work should stay focused on the current Package Wizard: generated local files, package model JSON, manifest overlay JSON, visitor-AI digest output, copy-paste decks, optional LLM Wiki plan output, and canonical starter ZIP links.
4. Agentic-system work should keep execution, tools, approvals, tracing, interruptions, orchestration, and managed memory with the chosen runtime while UAIX records portable UAI-1 evidence, Project Handoff memory, support boundaries, and release records that survive the run.
5. Future tooling language should remain planned or research-track unless the public page, matching machine artifact, reproducible evidence, implementation or package proof when needed, and dated release trail all agree.

## Roadmap Work Documentation Ledger

Use this ledger whenever roadmap work changes what readers or future agents should believe.

1. Document roadmap work where readers can verify it: keep `/en-us/roadmap/`, `/wp-json/uaix/v1/roadmap`, this file, focused tests, `AGENTS.md`, `readme.human`, and `.uai/progress.uai` aligned when roadmap truth changes.
2. Keep source leads bounded: active intake files, Reports, archived source material, and AIWikis cold memory can inform work, but they are not current UAIX truth until promoted into current docs, public pages, machine artifacts, tests, release notes, roadmap state, or handoff records.

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 Roadmap; Status; How To Use This Document; No Longer Roadmap Items; Roadmap Principles; Today Focus Path; Roadmap Work Documentation Ledger; Current Roadmap Work Queue. 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-1116 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "UAIX Roadmap",
    "source_site":  "uaix.org",
    "source_url":  "https://uaix.org/",
    "canonical_url":  "https://aiwikis.org/uaix/files/raw-system-archives-uaix-recent-work-sweep-2026-05-03-docs-roadmap-md-e656937b/",
    "source_reference":  "raw/system-archives/uaix/recent-work-sweep/2026-05-03/docs/roadmap.md",
    "file_type":  "md",
    "content_category":  "memory-file",
    "content_hash":  "sha256:e656937b9413a1f35f07a926f3f3292accb3bfa935296e83ec11018cd072c010",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-05-02T19:39:17.7057324Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-1116",
    "duplicate_role":  "primary",
    "related_files":  [

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