Well-known files describe public purpose, package posture, and runtime authority false.
Phase 2.46 / v1.5.65
Developers
Developer routes expose schemas, validators, examples, OpenAPI-style metadata, and UAI-1 records for local-first integrations.
Machine discovery console
Every impressive human surface has a machine-readable twin.
Use these routes to inspect live identity, explicit route tables, UAI envelope shape, current quality gates, and agent guidance without gaining runtime authority.
01 / IdentityLocalEndpoint identity
Current package identity, public boundary, and metadata posture.
/.well-known/localendpoint.json
02 / OpenAPIOpenAPI profileRead-only route profile for public inspection and integration planning.
/.well-known/openapi.json
03 / RoutesPublic route indexExplicit human and machine route table with no generic runtime fallback.
/api/public-route-index.json
04 / Agent briefLLM-readable guideShort public guidance for AI systems reading the site.
/llms.txt
05 / EnvelopeUAI-1 exampleMachine-readable context wrapper with runtime authority kept false.
/api/uai-1/envelope/example.json
06 / QualityQuality gatesCurrent readiness signals, route clarity, and non-certification boundaries.
/api/quality-gates/status.json
Protocol relay
Public discovery becomes a local-ready contract.
The developer path turns the website into a deterministic handshake: agents read context, developers validate shape, evidence travels, and runtime authority still stops at Desktop.
UAIX and route contracts define what can be inspected before any local handoff.
Browser receipts, hashes, and quality gates make review portable without private endpoint data.
The public site prepares context; human-visible local approval remains on the device.
Protocol rule
Read context
Validate shape
Carry evidence
Deny runtime
Read-only agent firewall
Machine-readable does not mean machine-authorized.
The developer surface gives agents enough structure to understand LocalEndpoint, compare public contracts, and produce review evidence without crossing into localhost probing, credential requests, command dispatch, or autonomous execution.
01 / Discover
Read public guidance
Agents start with the public brief and identity records.
02 / Inspect Follow explicit routesThe route index is the map; no generic runtime fallback is implied.
03 / Validate Check shape locallyValidation proves manifest shape and redaction posture, not runtime authority.
04 / Handoff Stop before authorityAnything actionable belongs to a human-visible Desktop review.
Agent firewall
Read-only discovery
Schema inspection
Evidence allowed
Runtime denied
Agent boot sequence
Read the public surface like an AI, but keep authority human.
The correct agent path is deterministic: discover identity, inspect the explicit route table, validate schema shape, check quality gates, produce evidence, and stop before runtime execution.
- 01Read
/llms.txtand/.well-known/ai-agent.json - 02Confirm routes in
/api/public-route-index.json - 03Inspect UAI fields through
/api/uai-1/conformance-pack.json - 04Check gates at
/api/quality-gates/status.json - 05Validate locally; share redacted evidence only
- 06Hand off to Desktop for human approval
Agent contract Metadata is readable. Runtime authority is false.
Allowed: route discovery, schema inspection, example validation, quality evidence review.
Denied: localhost probing, credential requests, public command dispatch, autonomous execution, certification claims.
Declare endpoint scope
Use schemas and examples to describe what a local endpoint is allowed to expose.
Generate evidence
Validate payloads, redact sensitive fields, and share reviewable artifacts instead of private data.
Keep authority local
Route public discovery toward future desktop approval flows rather than browser-triggered execution.
Operating 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.