Operate
Contract designedPolicies
Deterministic, versioned, default-deny decisions bound to exact transaction payloads.
Pre-alpha documentation boundary
Examples describe accepted contracts unless explicitly marked implemented. They do not imply a deployed API, SDK, signer, or production environment.
Examples
Policy scopes#
Policies may apply at organization, environment, ecosystem, application, wallet, user, session, delegated signer, and agent boundaries.
- Deny precedence
- Explicit versioning
- Consent receipts
- Risk and assurance conditions
Decision binding#
The signer-facing decision must include the canonical payload digest, simulation digest, effective policy version, app and tenant context, assurance, audience, expiry, and replay ID.
Implementation status
Engineering status Review the engineering-readiness snapshot for current service boundaries. Contact the team before integrating a capability that remains gated.