Limited Browser Support

Limited-browser support is the L0/L1 promise: a client can still read useful public records when it cannot run JavaScript, click UI controls, authenticate, post data, call tools, store memory, or coordinate agents.

What to publish

Static HTML or text summaries for important pages.
JSON records for schemas, registry entries, examples, discovery, conformance levels, and error codes.
llms.txt, llms-full.txt, sitemap routes, and stable canonical links.
A fallback note when a feature needs browser rendering, tools, authentication, or human consent.

L0 and L1 validation

L0 and L1 profiles fail when they claim JavaScript execution or make JavaScript-only content the only path. Their safe default is to cite the static or JSON route and state what higher capability level is needed next.

Useful records

Capability-Adaptive Web Interaction for the full ladder.
Schemas, Registry, and Examples for machine-readable records.
Validator for checking the L0 and L1 examples.

Minimal Access Tier for URL-only chatbots

Limited-browser support now names a stricter Minimal Access Tier for clients that can only issue a public GET request with no body, no auth, no custom headers, and no JavaScript. That tier returns only a code and a public url; it never mutates state.

Agent Communication Operating Model

Agent runtimes execute. UAIX records the reviewed communication, memory, trust, evidence, and handoff boundary.

Use Agent Communication Operating Model when a human operator, coding agent, AI agent, or runtime implementer needs portable identity, intent, context, acknowledgement, status, blocker, memory proposal, validation evidence, correction, final report, or handoff records. The matching machine-readable assets are published through Schemas, Registry, Examples, and the Validator.

UAIX does not provide automatic sync, hosted messaging, runtime orchestration, official adapters, repository write execution, certification authority, or hosted import mechanisms.
Carcinus.org is a separate runtime/orchestrator example that may consume UAIX records. UAIX.org does not implement Carcinus runtime behavior and does not execute Carcinus workflows.
LocalEndPoint and other runtimes may consume the published UAIX records as external consumers; UAIX.org does not implement their project-specific runtime features.
Durable memory proposals stay separate from task execution records. Do not promote temporary endpoint statuses, session tokens, write tokens, beta platform instructions, local error traces, private keys, or API credentials.