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

Permanent dated UAIX report index for source research and proposal material, with support boundaries tied back to current public evidence.

  • 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.

Published UAIX reports

These dated reports preserve source Markdown research and proposal material as permanent public HTML pages inside the UAIX site shell. The report bodies are converted from the source files, while the page header, footer, navigation, outline, date, and source metadata are supplied by the UAIX publication theme.

Reading boundary: reports explain source proposals and rationale. They do not widen current support claims on their own; check AI Memory, Project Handoff, Roadmap, Changelog, and released evidence before repeating tooling, certification, generator, SDK, CLI, or endorsement language.

How to use this report index

Start with AI Memory when you want the broad public vocabulary, then Project Handoff when you want a pattern teams can use now. 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.