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

About

Contact and Review

Dedicated public operating path for launch-stage contact, contributor guidance, change proposals, and review packets.

  • Record UAIX-ABOU-0044
  • Path /en-us/about/contact-and-review/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-ABOU-0044
Surface
About
Access
Public and linkable

How to use this page

Use this page to assemble launch-stage contact, contribution, change-proposal, and review packets before they become public release records.

Review with

References and ContributorsGovernanceValidatorChangelog

Review Intake

Turn contact, contribution, and change requests into reviewable packets

Use this page as the current launch-stage public path for review packets while broader issue trackers, repositories, or contact desks remain future work.

Packet first

Name the affected record

Every request should identify the record family, canonical path, record code, change type, and expected public effect before it is treated as ready for review.

Evidence

Attach validator or package proof

Behavior changes should carry route responses, validator results, implementation evidence, or package smoke-test output with the proposal.

Locale parity

Keep English and zh-CN aligned

When a public page changes, keep Chinese copy, route expectations, and release notes current at the same time.

Review with

References and ContributorsDiscovery, attribution, and handoff context.GovernanceDecision trail and public operating posture.ValidatorEvidence path for message behavior.ChangelogDated public release trail.

Purpose

Contact and Review is the dedicated public operating path for launch-stage UAIX questions, contribution packets, change proposals, and release-linked review notes. It turns the contributor guidance that was previously scattered across governance, references, roadmap, and changelog pages into one route.

Current review intake path

Use this page as the public intake checklist before a change becomes launch truth. UAIX does not yet publish a separate public issue tracker, mailbox, forum, or repository queue on the site surface, so review packets should stay tied to canonical pages, machine-readable artifacts, validator evidence, and the dated release trail.

  1. Identify the affected record family: specification, schema, registry, example, validator, implementation, governance, discovery, packaging, or locale content.
  2. Link the clean canonical page path and include the page-level record code when one is visible in the document header.
  3. Attach the relevant machine artifact, fixture, validator result, package output, or route response when behavior changes.
  4. State whether the change is additive, corrective, policy-oriented, localization-only, or breaking.
  5. Update the English and zh-CN public copy together when the affected surface is visible to localized readers.
  6. Record launch-facing changes through Changelog and News when outside readers need a dated public trail.

Contributor guidelines

  • Use UAI-1, Schemas, Registry, Examples, and the Validator as the technical baseline before proposing protocol behavior.
  • Use Roadmap when the proposal affects future support language, bridge evidence, compact transfer, conformance maturity, developer tooling, or governance expansion.
  • Use Governance and Policy and Security when the change affects ownership, release discipline, privacy, accessibility, analytics, licensing, or security posture.
  • Use Implementations when a proposal affects packaged software, runtime mapping, release evidence, or support-claim scope.
  • Do not describe a local experiment, single passing validator result, unpublished implementation, or private note as current public support until the page copy, machine artifact, evidence, and release trail agree.

Change proposal template

Record family:
Canonical path:
Record code:
Change type:
Expected public effect:
Evidence attached:
Validator or package result:
Chinese copy impact:
Release-trail update:
Owner or reviewer:
Open questions:

Review windows and decision trail

During pre-launch, UAIX remains a focused single-publisher standards record. The current named public attribution and the canonical site records are the decision trail; broader reviewer rosters, public voting, certification, or partner governance should not be implied until they are published.

  • Decision rights: current launch decisions are published by updating canonical pages, machine artifacts, and release records together.
  • Review window: a change should stay planned until the affected public page, route, validator expectation, package evidence, and locale copy can be reviewed as one packet.
  • Release cadence: pre-launch changes are release-note-led rather than calendar-led; compatibility-affecting changes should receive a dated changelog entry.
  • Public comments: a comment becomes part of the public record when its disposition is reflected in an updated canonical page, roadmap item, changelog entry, news summary, validator expectation, or implementation record.

What to include before launch review

  • Canonical page and route links, never query-string aliases or screenshots as the source of truth.
  • Machine-facing route responses when the change affects API Reference, discovery, roadmap, adoption kit, conformance pack, schemas, registry, examples, or validation.
  • Package build, smoke-test, launch-audit, or implementation-track evidence when the change affects distributable software.
  • Updated zh-CN content when public localized readers will see the new page, route, or release statement.

Next step

Start with References and Contributors for discovery and attribution context, use this page to assemble the review packet, then carry the public decision through Governance, Roadmap, Changelog, and News as needed.