Talero maintains machine-readable runtime contracts for release engineering. The public summaries describe integration boundaries without publishing an attacker-ready map of internal surfaces.
A static artifact is a snapshot. Confirm live method availability and runtime posture against the deployment you use.
| Evidence | Purpose | Integration meaning |
|---|---|---|
| Release inventory | Tracks node methods, routes and capabilities for build and audit workflows | Does not grant network access |
| Deployment policy | Enables a reviewed subset for a role and environment | Can change independently of source inventory |
| Live response | Reports the current gateway or node decision | Authoritative for that request and deployment |
node-runtime-surface-contract.json
Public gateway endpoint, bounded request contract and the separation between JSON-RPC, node REST and Explorer REST.
node-runtime-capabilities.json
User-relevant capability posture and precise caveats, without internal feature or control-plane inventory.
node-release-manifest.json
Stable public network identity and publication boundary. It is not a signed binary-release attestation.
The node’s release process can bind cryptographic rules and runtime contracts into coordinated artifacts. These public JSON files are deliberately curated summaries, not the raw manifest, signer material, release hashes or operational configuration.