Agent Executability Matrix

L0-L7 executable path guidance for route records, browser form fallbacks, result URLs, restore/readback URLs, write credential response paths, and POST-blocked behavior.

Record UAIX-DOC-3084

Path /es-us/spec/agent-executability-matrix/

Use Canonical public record

The Agent Executability Matrix makes route guidance usable by agents with different tool limits. Endpoint lists are not enough; each route should say which level can complete the flow, where the result appears, how restore/readback works, and what to do when POST or authentication is blocked.

Executable guidance is more than endpoint discovery. Route records should name the ability level, method, content type, side-effect status, required fields, result URL field, restore/readback URL field, write credential response path, browser-form equivalent, GET safety, and POST-blocked fallback.

Level	Executable path	Required route guidance
L0	Read-only route discovery	Static page, sitemap, `llms.txt`, or public GET route names the next public URL or no-op review URL.
L1	Manifest/schema discovery	Machine record names schema, safe-read status, unsupported actions, and capability limits.
L2	Browser-open plus form submission	Browser-targeted writes provide a visible form or browser-open workflow when browser agents are a target.
L3	Structured HTTP JSON POST	POST route names content type, required fields, result URL, restore/readback URL, and structured errors.
L4	Authenticated owned mutation	Owned mutation names write credential response path, secret handling, audit, expiry, and idempotency.
L5	Restore/readback verification	Create or update flow exposes a public-safe restore/readback route.
L6	Multi-agent handoff/reporting	Handoff names task history, owner, role, blocker/no-op behavior, final report, and evidence.
L7	Site-specific capability negotiation	Site manifest names capability negotiation, browser fallback, POST fallback, and unsupported-operation response.

Machine-readable companion: /spec/agent-executability-matrix.json.

Route-record contract

Records that describe create, update, restore, handoff, or negotiation routes should declare method, content_type, side_effect_status, required_fields, result_url_field, restore_readback_url_field, write_credential_response_path, browser_form_equivalent, get_safety, and post_blocked_fallback.

Dogfood lesson

The Carcinus blank-agent test found that a browser-limited agent could discover a JSON POST endpoint but could not execute arbitrary JSON POST. UAIX guidance now treats an L2 browser-open plus form-submission path, or a named POST-blocked fallback, as part of the public compatibility contract whenever browser agents are a target.

Validation warnings

Warn when side-effecting GET links are presented as general discovery shortcuts.
Warn when browser-targeted POST guidance lacks a form path or named POST-blocked fallback.
Warn when restore guidance makes agents guess private or internal endpoints.
Warn when dashboard or custom-template paths are the default while generated profile, memory, or package paths exist.