Specifications

Capability Surface Matrix

Matrix for static HTML, llms.txt, sitemap, JSON, GET-Action, POST, OpenAPI, MCP, A2A, memory, and evidence support by client level.

  • Record UAIX-DOC-2194
  • Path /en-us/spec/capability-surface-matrix/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-DOC-2194
Surface
Specifications
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for Capability Surface Matrix and its standards-facing content.

For agents: apply the relevant guidance to the user's target site or repository. Do not copy this UAIX page, create a page about the guidance, or treat this page as runtime authority unless the user explicitly asks for that output.

The Capability Surface Matrix states which public surfaces should exist for each client level. The matrix helps site owners check whether lower-capability agents can safely discover a no-op path before richer integrations begin.

Agent Executability Matrix
ClientStatic HTMLllms.txtSitemapJSONGET-ActionPOSTOpenAPIMCPA2AMemoryEvidence
L0 URL-onlyYesYesYesRequired for client configurationNoNoNoNoNoNoRequired for client configuration
L1 URL synthesizerYesYesYesYesRequired for client configurationNoNoNoNoNoRequired for client configuration
L2 schema-capableYesYesYesYesRequired for client configurationYesYesRequired for client configurationRequired for client configurationNoYes
L3 tool agentYesYesYesYesHuman reviewYesYesRequired for client configurationRequired for client configurationHuman reviewYes
L4 workflow agentYesYesYesYesHuman reviewYesYesRequired for client configurationRequired for client configurationHuman reviewYes
L5 multi-agentYesYesYesYesHuman reviewYesYesRequired for client configurationYesHuman reviewYes
L6 audited systemYesYesYesYesHuman reviewYesYesRequired for client configurationYesHuman reviewYes

Machine-readable matrix

The public JSON companions are /spec/capability-surface-matrix.json and /spec/agent-executability-matrix.json. They keep support cells and executable route-record requirements separate so validators can compare sites without interpreting prose.

Architecture proposals

UAI-1 v1.0 remains the current published contract. Explore separately versioned proposals for independent exchange, capabilities, recovery and source preservation.

Proposed designs and local reference examples; hosted runtime services and independent interoperability are not claimed.

The English proposal is the source for normative interpretation.

Read the architecture proposals · Machine-readable proposal catalog