UAI-1 is the current public message standard for structured AI-to-AI communication.
UAIX shield mark Public interoperability charter UAIX.org Universal Artificial Intelligence Exchange Public standards publication
Current UAI-1
  • Current version UAI-1
  • Plain-English definition Open message format for auditable AI-to-AI exchange
  • Current attribution Michael Joseph Kappel, MCP
  • Start here Get Started, Project Handoff, UAI-1, validator, roadmap, and changelog

Reports

Reports

Selected historical UAIX report index for source research and proposal context, with current records and AIWikis evidence boundaries named first.

  • Record UAIX-REPT-0070
  • Path /en-us/reports/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-REPT-0070
Surface
Reports
Access
Public and linkable

How to use this page

Use this page as part of the current Reports public record, then follow its linked standards pages for the next step.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

Selected historical UAIX reports

This page keeps a small set of dated source reports available for context, but the current UAIX standard should be read from active pages, machine-readable manifests, schemas, validator evidence, package records, and the changelog before these historical reports. The report bodies preserve source proposals and rationale; they do not widen current support claims on their own.

Current record first

Start with AI Memory, Project Handoff, UAI-1, the AI Memory Package Wizard, .uaix Package Format, Changelog, and public evidence manifest when you need current implementation posture. Use this report index only when you need background rationale, source-history context, or authority-boundary explanation.

How to use this report index

Use the relationship audit when you need the AIWikis, LLMWikis, and UAIX authority split. Use the LLM Wiki comparison reports when you need the boundary between knowledge accumulation and repository handoff. Use the AGENTS.md .uai linking specification for exact link and record details, then use the refining report when you need deeper background on repository-native .uai structure, validation, interoperability, and security considerations.

Evidence discipline for reports

Use reports as source leads, not as automatic current truth. A report recommendation becomes UAIX authority only after the useful conclusion is promoted into a current public page, machine-readable artifact, roadmap state, changelog entry, test, release package, or handoff record.

  • Primary record first: prefer schemas, registry entries, examples, validator output, route behavior, release notes, and current docs over commentary.
  • Claim-evidence split: label what is published today, what is planned, what is research-track, and what was rejected or blocked.
  • Promotion trail: keep the source report archived, then cite the durable target that adopted the conclusion.
  • Freshness check: re-check roadmap, changelog, and machine artifacts before repeating claims about adapters, SDKs, certification, hosted generation, sync, or conformance.

AIWikis long-memory evidence

Bulky source-history and preservation proof belongs in AIWikis long memory after review, not as an expanding UAIX visitor page. The current history-consolidation evidence pointer is recorded in public-evidence-manifest.json and preserved at raw/uaix/reports/2026-06-16-history-consolidation/manifest.json with source checksums and support-boundary notes.

This AIWikis evidence path is a retrieval aid. It is not live publication proof, automatic synchronization, certification, endorsement, hosted runtime behavior, or a replacement for current UAIX public pages and root discovery files.