Version, profile name, route context, and public metadata help agents understand what they are reading.
Phase 2.46 / v1.5.65
UAI-1 Envelope
UAI-1 envelope examples show machine-readable metadata shape without granting runtime authority.
UAI-1 envelope console
Metadata-only UAI-1 envelope.
The envelope lets agents inspect LocalEndpoint identity, route context, boundary flags, and evidence references without receiving runtime authority.
Route index, OpenAPI profile, field registry, and agent brief are reference links, not control channels.
A machine-readable envelope is not permission to run a local endpoint, fetch localhost, or dispatch commands.
Use envelope data with validator receipts and Desktop review instead of hidden automation.
Canonical metadata wrapper for public route context and boundary flags.
ConformanceConformance packMachine-readable expectations for envelope shape and validation behavior.
FieldsField registryNamed fields agents can inspect without receiving runtime capability.
TransportTransport bindingsTransport metadata describes shape without opening a local channel.
OpenAPIOpenAPI profilePublic endpoint descriptions for route discovery and review.
Agent briefllms.txtPlain agent instructions for public-safe interpretation and no-control boundaries.
Envelope describes public context
The envelope can identify package version, profile, route intent, and boundaries.
Envelope JSONRuntime authority remains false
A machine-readable envelope is not permission to run a local endpoint or command.
Technical boundaryHumans stay in the loop
Use envelope data with validator receipts and Desktop review instead of hidden automation.
Desktop pathOperating boundary
Public clarity, local authority.
This public site is static metadata and does not dispatch desktop commands, probe localhost, upload files, collect telemetry, request credentials, or claim runtime safety certification.