Repository boundaries
Gather live evidence
auths-proof-appsCarry proof bytes
auths-proof-exchangeResolve authority
auths-proofRun sealed command
auths-proof-appsDependency direction
Section titled “Dependency direction”auths-proof-exchange ---> auths-proofauths-proof-apps ---> auths-proof + auths-proof-exchangeauths-proof -X-> auths-proof-exchangeauths-proof -X-> auths-proof-appsauths-proof
Section titled “auths-proof”Owns the offline protocol kernel, canonical model and codec, pure ports and registries, deterministic evidence verification, WASM verification, pure authoring, canonical core corpus, and fuzz targets.
It reads no clock, network, filesystem, database, environment, replay state, budget state, receipt sink, application profile, or private key.
auths-proof-exchange
Section titled “auths-proof-exchange”Owns exchange messages, exact capability negotiation, bounded framing, typed peer observations, and memory, Iroh, HTTPS, TCP, Unix-socket, and offline-file transport adapters.
Networking carries proof. It never grants authority.
auths-proof-apps
Section titled “auths-proof-apps”Owns application profiles, live evidence acquisition, custody integrations, runtime orchestration, replay and budget state, receipts, configuration, reference applications, Auths Lab, and independent Go/TypeScript verifiers.
Placement test
Section titled “Placement test”If behavior cannot be evaluated deterministically from static proof bytes and explicit immutable context, it does not belong in the kernel.