Advanced Agent Support

Advanced agent support begins when a client can act, not just read. L3-L6 records require consent, idempotency, correlation, fallback, expiration, memory-review discipline, and evidence.

Level boundaries

L3 Tool Agent: tool calls, authentication, and posting only after explicit consent and idempotency.
L4 Workflow Agent: long-running external work with task status, timeout, correlation, fallback, and final report.
L5 Multi-Agent Runtime: external agent coordination with UAIX as the reviewed record and handoff boundary.
L6 Audited Agent System: provenance, audit log, validator result, consent record, memory review, and final-report evidence.

Do not widen the claim

UAIX does not run the workflow, coordinate agents, write repositories, or certify an implementation. It records the reviewed packet and validates the support claim shape.

Next records

Agent Consent Boundaries for approvals.
Agent Communication Operating Model for acknowledgement, task status, blockers, memory proposals, handoffs, final reports, and corrections.
Conformance Pack for positive and negative fixtures.

Progressive agent access

Advanced clients should prefer POST JSON, schema validation, consent records, idempotency, correlation, fallback behavior, and evidence packets. The GET-Action Pattern remains a bounded L0/L1 fallback and is not a replacement for POST endpoints.

Use Minimal Access for public read-only URL resolution.
Use GET-Action Security before publishing any URL-triggered action fallback.
Use Progressive Agent Access to escalate from URL-only reads to POST JSON, discovery manifests, handoff packets, and public-safe audit evidence.

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.