Architecture without exposing operations.
This section documents integration contracts, deployment patterns and trust boundaries. Internal hostnames, filesystem layouts, private ports and operational endpoints are intentionally excluded.
OpenProof
Identity architecture, provider federation, passkeys, wallets, OAuth/OIDC and self-hosting boundaries.
↓↯Remote operations
Patterns for controlled diagnostics and administration without publishing a private control-plane endpoint.
Documentation contract
Public infrastructure documentation should explain interfaces developers need to integrate with while keeping private topology and operator-only details out of the public surface.
Hostnames, ports and paths shown in guides should be placeholders unless they are intentionally public product identifiers.
Remote operations
Administrative tooling should sit behind an authenticated control plane with explicit scopes, audit logging and least-privilege access. Publish the integration model; keep the actual operator endpoint private unless there is a deliberate reason to expose it.