Capabilities, guarantees, and limits of this deployment
Self-describing contract surface. Hit once at boot to discover what’s wired up, what the ledger promises, and what the hard limits are, instead of hardcoding assumptions.
Three independent version fields:
ledger_capabilities_version: calendar-versioned shape of this document. Bumps when sections are added/renamed/removed. Pin against this if you parse the body.api_version: the URL-prefix version (v1). Bumps on breaking changes to resource paths or shapes.release: the running build. Useful for debugging; do not gate behavior on it.
Authorizations
OAuth 2.0 client_credentials grant. Send client_id:client_secret
as HTTP Basic, or as form fields. Tokens are HS256 JWTs valid for
one hour (configurable). Decode them at jwt.io.
Response
ok
"2026-01"
"v1"
"0.1.0"
What the ledger promises about correctness. Each key is a property the deployment will not violate.
capabilities Lifecycle state of the caller's tenant. suspended
and terminated tenants can still read (so they can
export); writes are rejected with tenant_suspended
(403). Dashboards should surface a banner when this
is not active.
active, suspended, terminated