Specified
Interfaces, permission model, evidence requirements, failure modes and the conformance checks a release must pass.
Workspace & infrastructure · Concept
Capabilities with boundaries attached.
Each capability in SovereignExecution is specified as a contract: scope, permission, evidence and failure behaviour.
01
The five contracts
Numbered for reference; the order is not a priority.
- 01. Execution isolation and deployment control
-
Defined as a scoped contract: the product states what it may touch, what it may change and what it must record.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 02. Policy-bound workload authorization
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 03. Local, private and cloud execution selection
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
Scope is attached to the capability, not to the caller, so delegation does not widen it silently.
Surfaces REST · MCP · CLI
- 04. Deterministic evidence and replay
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
The same capability is reachable from the application, the API and the agent surface without a second implementation.
Surfaces REST · MCP · CLI
- 05. Secrets, budgets and lifecycle enforcement
-
Specified with its own failure modes, limits and evidence requirements before it is exposed to an agent.
The same capability is reachable from the application, the API and the agent surface without a second implementation.
Surfaces REST · MCP · CLI
02
What is specified, and what is not
A capability in a specification is not a shipped feature.
Not claimed
Running deployments, measured performance, third-party certifications or integration approvals.