Resilience Network API
The API is live at https://resilience-by-design.com/api/network/v1. Discovery, the network catalogue, signing key and promoted release metadata are public; workflow writes require a scoped bearer credential.
Access model
Credentials are issued to a named network service account after governance review. Before any operational scope becomes active, the integrating entity and the Resilience tool controller must sign the exact hash of an immutable service agreement. Sigma Tech LLC is the initial controller. Separate scopes cover observation submission, candidate preparation, independent evaluation, human promotion, graph projections and receiving-network sandbox tests. Producer credentials cannot evaluate or promote their own candidate. Tokens are shown only when issued, stored as hashes by the service and can be revoked.
Graph access
Entity graph access is limited to projections named in the effective agreement and mediated through the API. PostgreSQL credentials, database coordinates and cross-entity graph access are never supplied through this service. The machine-enforced agreement is a governance control and must still receive appropriate legal review by both parties.
Safety and evidence
Payload schemas require synthetic_only: true, allow_live_actuators: false, deterministic seeds and explicit provenance. Unknown fields—including caller database coordinates and deployment instructions—are rejected. Raw observations, evaluations, promotion decisions, releases and audit-chain events are append-only. Promoted OKF packages use Ed25519 signatures and always require a new sandbox test in the receiving network.