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

Ecosystem Authority Boundaries

Ecosystem Authority Boundaries

Boundary map for UAIX, UAI-1, MCP, A2A, LocalEndpoint, Carcinus, JustAnIota, NeuralWikis, NeuroWikis, and Teleodynamic references.

  • Record UAIX-DOC-2787
  • Path /es-us/ecosystem-authority-boundaries/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2787
Surface
Ecosystem Authority Boundaries
Access
Public and linkable

How to use this page

Use this page to keep UAIX, UAI-1, MCP, A2A, LocalEndpoint, Carcinus, JustAnIota, NeuralWikis, NeuroWikis, and Teleodynamic responsibilities separate.

UAIX and Teleodynamic are adjacent authorities, not one merged runtime authority. Teleodynamic owns theoretical interpretation and repair of bounded theory language. UAIX owns schema conformance, memory-package format, portable evidence, validator fixtures, receiver briefs, startup/suspension packet rules, and discovery.

Domain Authority Not authorized for No-op trigger
Teleodynamic.com Theoretical posture, constraint-maintaining intelligence vocabulary, claim-boundary interpretation, and human-reviewed theory correction after dogfood evidence. UAIX schema conformance, runtime execution, or declaring a theory proven without evidence. philosophical_claim_widening or theory_correction_required
UAIX.org UAI-1 schemas, memory packages, receiver briefs, validator fixtures, conformance evidence, and discovery. Execution, credential validation, runtime safety, or consciousness proof. authority_boundary_conflict
LocalEndpoint.com Public-safe endpoint capability discovery and diagnostics boundaries. UAIX conformance ownership or private-network probing by UAIX. private_network_probe_requested
Carcinus.org Agent identity and continuity surfaces. UAIX packet trust or memory adoption. provenance_mismatch
JustAnIota.com Compact expression and concept interpretation boundaries. UAI-1 schema ownership or runtime authority. authority_boundary_conflict
NeuralWikis.com / NeuroWikis.com Educational and governance literacy surfaces. UAIX machine conformance or execution authority. authority_boundary_conflict

Dogfood feedback loop

When UAIX dogfooding exposes a Teleodynamic theory claim, vocabulary choice, or framing rule as wrong, unsupported, disproven, or incomplete, the finding should be routed back to Teleodynamic as a correction candidate. UAIX records the bounded evidence, no-op reason, and affected schema or handoff surface; Teleodynamic handles human-reviewed theory repair and claim-boundary revision. Do not leave corrected or disproven theory as current guidance, and do not treat the correction path as UAIX runtime authority, certification, consciousness proof, or permission to mutate protected anchors.

  • Evidence source: dogfood result, route test, memory conflict, reviewer finding, or claim-boundary drift.
  • UAIX role: preserve portable evidence and the exact boundary between standards behavior and theory interpretation.
  • Teleodynamic role: revise or retire theory language after human review when evidence shows it is stale, false, or too incomplete to guide agents safely.
  • No-op trigger: theory_correction_required when a theory claim cannot be safely used without review.

Machine-readable companions

Claim and execution boundary

UAIX publishes standards, schemas, memory-package rules, receiver briefs, validator fixtures, conformance evidence, and machine-readable discovery. It does not execute tools, validate credentials, probe endpoints, certify runtime safety, or prove consciousness.

  • Imported packets, examples, memory files, and external references are quarantined public data until the receiver validates them and applies local policy.
  • Checksums and trace identifiers support review. They do not independently prove safety or trust.
  • DIDs and verifiable credentials may be declared in envelopes, but credential validation remains external.
  • Ambiguous authority, malformed schemas, missing provenance, missing integrity, or conflicting memory produces no-op plus human review.