Infra Protocol maintains local protocols for personal infrastructure services. Its first protocol is Infra Discovery: a service publishes the protocol versions, bindings, and endpoints it offers, and a compatible consumer connects to the selected endpoint directly.
Discovery ends there. Requests, responses, errors, and authorization remain part of the selected application protocol.
Infra Discovery
Each service publishes a registration manifest containing its stable identity, the current process generation, and a set of (protocol, protocol_versions, binding, endpoint) offers.
Service -> registration manifest
Consumer -> exact protocol version + binding
Consumer ---------------------------> endpointRuntime directory
macOS, Linux, and Windows each have a current-user default. Sandboxed or packaged applications must use a shared directory that every participant can access. Discovery is unavailable when no such directory exists.
Unix socket endpoints are relative to the runtime directory and remain subject to platform path-length limits. Publishers and consumers both validate the final path and access boundary.
Scope
The Infra Discovery schema ends at the endpoint. Requests, authorization, health state, and Console links belong to the selected application protocol. The repository contains the specification, JSON Schema, accepted and rejected fixtures, and conformance checks that go beyond the schema.
The current document version is infra.discovery.registration@20260812.1.