The runtime describes itself.
Machine-readable contracts expose the node's exact public surface; the consensus manifest turns network cryptography into a verifiable inventory.
Public-safe is not unrestricted. Privacy, safe-mode, read-only, quota, role and gateway policies can still mask or deny a listed surface.
From inventory to proof
The consensus manifest is a cryptographically verifiable inventory — a CBOM — that binds the node's cryptographic rules and runtime contracts into one agreed network description. Every node confirms the same description.
Coordinated manifest transitions make cryptographic change explicit: participants move together from one agreed inventory and ruleset to the next. The mechanism is public; exact release-identifying cryptographic values are not.
Public machine-readable summaries
node-runtime-surface-contract.json
Public counts, policy categories and public-safe method and route lists.
node-runtime-capabilities.json
All 15 capability labels with status, maturity, exposure and precise publication wording.
node-release-manifest.json
Version, schema, chain ID and inventory counters only.