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

Implementations

WordPress Publication Track

Public site, packaging, and distribution track for the UAIX website and release packages.

  • Record UAIX-IMPL-0054
  • Path /en-us/implementations/wordpress-reference/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-IMPL-0054
Surface
Implementations
Access
Public and linkable

How to use this page

Use this track for the public site, packaging, launch checks, and release notes on UAIX.

When to choose this track

Use the WordPress Publication Track when you need the public site, packaging, release notes, discovery files, and distribution path for UAIX and UAI-1. This track turns the standard record into reviewable web pages, packages, exports, and launch checks; it does not become the identity of UAI-1.

What this track covers

WordPress owns the public presentation and distribution work. Normative authority still lives in UAI-1, the schema and registry records, the validator expectations, and the changelog. Treat the WordPress track as publication infrastructure and release evidence, not as a private fork of the standard.

Responsibilities

  • Publish the current specification, supporting pages, news, governance notes, references, and press assets.
  • Distribute installable themes and plugins in upload-ready packages.
  • Keep package links, public documentation, validation guidance, discovery files, and release notes aligned.
  • Support smoke testing and launch checks so the published packages remain installable, reproducible, and reviewable.

Current packaged deliverables

  • uaix-authority-theme.zip is the current public launch theme for UAIX.
  • uaix-theme.zip remains available as the packaged compatibility theme.
  • uaix-core.zip, uaix-modules.zip, ns12-locale-router.zip, and uaix-seo-sweep.zip carry the supporting plugin surface that keeps standards records, modules, locale-prefixed routes, canonical discovery assets, and clean public URLs installable.
  • WordPress release evidence should point back to the packaged ZIP family, current smoke-test results, and the linked release trail rather than to ad hoc local builds.

Public records owned here

  • References and Contributors for discovery links, attribution, and citation context.
  • The Changelog and News archive for migration notes, release summaries, and implementation updates.
  • Press for approved public language and reference material.
  • Governance for compatibility posture and change discipline.

What counts as evidence here

  • Successful packaging, smoke-test, and launch-check results.
  • Validator-backed examples, public schema alignment, and current discovery files.
  • Release notes and changelog entries that explain what changed, why it changed, and what readers should do next.

Current support-claim boundary

The WordPress track supports the public publication surface: canonical pages, packaged releases, discovery files, and linked release documentation tied back to the standard record.

  • A successful package build or smoke test supports a claim that the publication surface is release-ready for review.
  • A current public support claim for WordPress should stay scoped to published site delivery, packaging, routing, discovery alignment, and linked release records.
  • Do not use this track to imply broader runtime interoperability outside the published WordPress surface or outside the linked UAI-1 record.

When this track is release-ready

  1. Package outputs are installable and the public site renders the current canonical records correctly.
  2. Discovery files, route checks, validator references, changelog notes, and release summaries all point to the same public state.
  3. The release trail states what changed in the publication surface without implying new runtime support that has not been separately published.

Next step

After validating the publication track, continue to the .NET Bridge Track if the implementation also needs deeper runtime integration, and keep release evidence linked through References and Contributors, the Changelog, and News.