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

Agent Capability Framework

Agent Capability Framework

UAIX Agent Capability Framework for L0-L6 declarations, memory firewall posture, no-op triggers, receiver briefs, and portable conformance evidence.

  • Record UAIX-DOC-2784
  • Path /en-us/agent-capability-framework/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2784
Surface
Agent Capability Framework
Access
Public and linkable

How to use this page

Use this page to resolve the L0-L6 capability framework, memory firewall, no-op triggers, evaluation packet templates, and public evidence boundaries before claiming agent support.

The UAIX Agent Capability Framework makes L0-L6 capability declarations, memory firewall behavior, no-op rules, evaluation packet templates, and conformance evidence discoverable to humans and agents.

UAI-1 remains an open exchange contract for auditable AI-to-AI and human-to-agent handoff. It standardizes declared identity, provenance, lifecycle state, delivery semantics, trust declarations, typed errors, memory packages, receiver briefs, and portable evidence beside MCP, A2A, OpenAPI, LocalEndpoint, Carcinus, JustAnIota, NeuralWikis, NeuroWikis, and Teleodynamic. It does not replace those systems.

Level Label UAIX expectation No-op behavior
L0 Rule-Based Workflow / static format follower Reads static public text, Markdown, sitemap entries, and small JSON. No JavaScript, POST, tool, credential, memory, or execution authority is implied. No-op plus human review when schema, authority, or route intent is ambiguous.
L1 Basic Responder / prompt-bound assistant Fetches public JSON and follows explicit prompt-bound instructions. It cannot approve writes or private actions. Stop with human_review_required when requested work needs authority not present in the packet.
L2 Tool User / approval-bound co-pilot Understands schemas and can prepare tool-call proposals, but write-capable behavior requires explicit human approval. Prepare no-op justification when approval, integrity, or provenance is missing.
L3 Bounded Operator / autonomous within explicit limits Operates inside stated limits when authority, policy, timeout, provenance, and evidence are explicit. Stop on boundary conflict, missing checksum, credential validation request, or private-network probe request.
L4 Domain Actor / full-domain autonomous worker under boundaries Handles a bounded domain across a workflow with trace, review checkpoints, typed errors, and final evidence. Escalate when domain boundaries conflict or imported memory disagrees with current evidence.
L5 Multi-Agent Collaborator / peer coordination with evidence handoff Coordinates multiple agents while UAIX carries portable evidence, role boundaries, memory proposals, and handoff receipts. Use human review if role, authority, memory custody, or provenance is ambiguous.
L6 Meta-Coordinator / orchestrates teams and long-running cross-domain memory Routes evidence across teams and memory systems under explicit boundaries. It is not deployed proof of consciousness or unrestricted autonomy. Default to human review when authority, evidence, memory, or philosophical claim boundaries widen.

Core records

Evaluation packet templates

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.