Official reference publication Stable protocol, registry, and implementation records
Public interoperability charter UAIX My WordPress Blog
  • Record families Specification, registry, examples, implementations
  • Publication mode Versioned public reference surface
  • Reading posture Dense, citation-ready, and mobile-safe
  • Primary use Research, implementation, validation, and governance

Universal Artificial Intelligence Exchange

Institutional charter

An official publication surface for protocol standards, machine-readable records, and deployable interoperability artifacts.

Citation-ready Versioned paths Mobile-safe archive

A lightweight protocol layer for AI-to-AI communication.

UAIX defines a structured exchange format that enables AI agents, models, and services to communicate intent, context, and data across environments without dependency on specific frameworks, vendors, or architectures.

Read UAI-1 Specification Open Validator
Publication posture
Open, versioned, citation-ready public reference surface
Canonical paths
/specification, /schemas, /registry, /implementations, /governance
Reference audience
Implementers, tool builders, researchers, publishers, and standards readers
Publishing goal
Expose the protocol, records, and runtime artifacts without marketing chrome
Current protocol UAI-1 Draft
Primary surface Spec + Schemas + Examples
Reference runtime .NET + WordPress
Positioning Open protocol layer

Core records

Surface characteristics

  • Compact, citation-friendly publishing surface
  • High-density reference layout with persistent navigation
  • White institutional presentation instead of a product-marketing shell

Charter discipline

  1. Normative first Protocol text, schemas, examples, and packages are published as one public record rather than scattered product collateral.
  2. Institutional reading Readers should see scope, record codes, document types, and implementation routes immediately without ornamental whitespace.
  3. Operational continuity The same surface that explains the protocol also exposes the routes, artifacts, and packages needed to deploy it.

Public Register

Canonical records and reference surfaces

UAIX is published as a dense institutional reference surface: readers should be able to move from scope to specification to schemas to deployable packages without leaving the public record.

REC-01

UAI-1 specification

Canonical exchange structure, document scope, and processing expectations.

Normative record
Open record
REC-02

Schemas and registry

Public schema targets, identifiers, and interoperability-facing records.

Machine-readable artifacts
Open record
REC-03

Examples and fixtures

Readable exchanges, validation fixtures, and implementation-oriented examples.

Reference examples
Open record
REC-04

Reference implementations

WordPress packages, .NET bridge integration, and portable module tracks.

Distribution surface
Open record
REC-05

Governance and changelog

Publish the normative spec, machine-readable schemas, examples, validators, and reference implementations as versioned, redistributable artifacts.

Policy record
Open record

Protocol Orientation

Interoperability presented as infrastructure

Universal Artificial Intelligence Exchange (UAIX) is a lightweight, platform-agnostic protocol designed to standardize communication between artificial intelligence systems. It is published as an interoperability layer rather than as a closed platform shell.

Message structure

A consistent exchange envelope for identity, intent, context, payload, outputs, and errors.

Portable by design

The protocol is meant to move across WordPress, .NET, services, agents, tools, and future runtimes.

Specification-backed

Normative text, schemas, examples, and implementation notes are published as distinct surfaces.

Reference Exchange

A readable exchange record

Message example JSON exchange 
{
  "uaix_version": "1.0",
  "type": "intent",
  "source": "agent.alpha",
  "target": "agent.beta",
  "payload": {
    "action": "retrieve",
    "resource": "trackable",
    "id": "ABC123"
  }
}

Working Context

Implementation, governance, and research guidance

Implementation priorities

  • Keep exchange structure stable across WordPress, .NET, services, and future runtimes.
  • Publish schemas and examples next to normative text so implementers can verify against the same source.
  • Distribute runtime packages in uploadable, slug-correct archives for operational reuse.

Publication principles

  • Prefer stable URLs, human-readable headings, and machine-readable artifacts over promotional framing.
  • Treat the homepage as a directory and register, not as a landing-page campaign surface.
  • Keep governance, change history, and interoperability notes visible at the same level as the protocol text.

Research surfaces

  • Protocol overview and scope framing for readers evaluating UAIX as infrastructure.
  • Examples, registry entries, and implementation notes that can be cited or mirrored.
  • Operational distribution artifacts that help move from reading to deployment without ambiguity.

Implementation Layer

Reference stack

  • UAIX WP Core for public distribution and integration entry points
  • .NET API bridge for runtime handoff and backend interoperability
  • Redistributable modules for portable adoption

Publishing Direction

Immediate public IA

  • Get Started
  • Specification / UAI-1
  • Schemas, Registry, and Examples
  • Implementations, Tools, and Governance