Security
Custody, signing isolation, application authority, release gates, and evidence boundaries.
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
Custody target#
The target architecture prevents the ordinary control plane, host application and backend services from unilaterally spending a user's assets. User-controlled shares and isolated signer workloads remain required. One owner may administer the infrastructure; the design is not yet implemented or verified as production custody.
Signing plane#
Signing is isolated from the SaaS control plane with minimal ingress, service identity, replay protection, immutable decision context, restricted egress, separate deployment approval, and no dashboard access to raw signing material.
Release gates#
Real-value release requires retained internal cryptographic and implementation review, signer penetration testing, ceremony verification, smart-contract assessment where applicable, export isolation tests, restore exercises, incident drills and owner approval of accurate custody claims and the exact release. Corey and Codex may perform the internal work; outside reviewers, independent custodians and two-person sign-off are not mandatory.
- No certification claims
- No audit claims
- No availability claims
- No mainnet default
Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.