Standards

UAIX Capability Ladder

L0-L6 capability ladder for static readers, structured fetchers, browser-assisted agents, tool agents, workflow agents, multi-agent runtimes, and audited systems.

  • Record UAIX-STND-2257
  • Path /en-us/standards/capability-ladder/
  • Use Canonical public record

Document status

Public standards page Published on UAIX as part of the current public standards record
Code
UAIX-STND-2257
Surface
Standards
Access
Public and linkable

How to use this page

Use this page as the canonical public reference for UAIX Capability Ladder 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 UAIX capability ladder lets one standards surface degrade safely across very different clients. The level describes what a client can reliably read or do; it never grants permission by itself.

UAIX Capability Ladder
LevelClient postureMay doMust not implyFallback
L0Static or limited browserRead static HTML, text, Markdown, sitemap, llms, and small JSON.JavaScript, posting, auth, tools, memory, or coordination.Plain links and copyable text.
L1Structured fetchFetch predictable JSON, schemas, registry, examples, and manifests.Rendered UI parity or write-capable behavior.Low-token JSON and stable routes.
L2Browser-assistedInspect rendered UI and compare it to static evidence.Autonomous writes, auth, or tools.Static/JSON parity notes.
L3Tool agentCall tools, authenticate, or post only with consent, idempotency, and evidence.Long workflow ownership or memory promotion.Blocker record and human review.
L4Workflow agentRun external long tasks with correlation, task status, timeout, and final report.Unreviewed memory promotion or agent coordination.Status, blocker, and final-report packets.
L5Multi-agent runtimeCoordinate external agents while UAIX carries reviewed records and handoffs.UAIX-hosted execution or unverifiable trust claims.Unsigned reference handoff or verified receipt only when verifier evidence exists.
L6Audited agent systemAttach provenance, audit digest, consent, validator output, and public-safe receipts.Certification, endorsement, or trust without local policy.Public-safe audit digest and explicit exceptions.

Minimum rule

When capability is unknown, downgrade to L0/L1. Name the unsupported feature, return static or JSON evidence, and request human-mediated review before writes, auth, tools, memory, coordination, or audit claims.