Security Properties
SovereignClaw documents the formal guarantees behind its AI agent runtime security model: nine enforced properties, 1,345 workspace tests passed in the October 7, 2026 release run, and no execution without a signed Gate artifact. The full verification evidence is published on the proof page.
SovereignClaw enforces AI agent safety through architecture, not prompts, filters, or guardrails. These 9 formal security properties (S1–S9) are mechanically enforced and covered by automated tests, and there is no execution without a signed Gate artifact.
These properties explain why SovereignClaw is more than a set of AI guardrails. They define what the runtime must enforce before any action reaches an adapter, and they are verified through automated testing rather than operator promises. For context, review the execution pipeline, the framework mappings, and the published paper. Published on SSRN (ID 6290760). The DetGate execution-gating method behind SovereignClaw is patent pending with the USPTO.
Formal Security Properties (S1–S9)
S1
Adapter Reachability
No operation reaches the Adapter without a valid Gate artifact bound to IR hash, policy bundle, adapter identity, and nonce.
S2
Frozen Input
All SovereignIR inputs canonicalized and byte-frozen before risk tier computation. Identical intents produce identical hashes.
S3
Fact Recalculation
Tier-driving facts recomputed from operation semantics. Model-supplied facts never trusted. Mismatches are flagged and escalate risk.
S4
Deny Dominance
Any Deny is final. No component may downgrade a restrictive decision.
S5
Nonce Uniqueness
Every execution requires a unique nonce. Replays are rejected before any side effect.
S6
Adapter Binding
Artifacts cryptographically bound to a specific adapter identity. Tokens for one adapter invalid on any other.
S7
Multi-Party Approval
T2 requires verified threshold signatures from distinct operators, with a default quorum of 1 of 2. Insufficient quorum is a denial. T3 is refused by default policy, and signatures cannot override a deny.
S8
Tamper Evidence
Every permitted execution emits an Authority Receipt signed with Ed25519 and SLH-DSA-SHA2-256f, chained in an append-only hash chain with Merkle anchors, and verified against operator-pinned public keys.
S9
Skill Publication Binding
Runtime artifacts and receipts carry published skill digest, tenant scope, and correlation IDs.
Enterprise Security Features
- Multi-tenant isolation with daily quota enforcement
- Per-tenant credential vaults with time-limited lease access
- SSO/SCIM: Okta, Azure AD, Google Workspace → approval quorums
- Async approval workflows: configurable quorum, TTL, escalation chains
- Observability: Prometheus and Datadog export
- Ed25519-signed skill manifests - unsigned skills blocked at gate
- Control mappings for SOC 2, NIST, HIPAA, and ISO 27001
- Secret rotation and drift detection
- Compliance metrics: JSON + CEF for SIEM ingestion
- OWASP Agentic (AA1 to AA10) control mapping
Frequently Asked Questions
How many security properties does SovereignClaw enforce?
SovereignClaw enforces 9 formal security properties (S1-S9) across every execution path, covered by automated tests in a 33-crate Rust workspace. The October 7, 2026 release run passed 1,345 workspace tests with zero failures.
Can an unsigned execution occur in SovereignClaw?
No. There is no execution without a signed Gate artifact. Every execution requires a valid Gate artifact cryptographically bound to the canonical IR hash, policy bundle, adapter identity, and nonce.
What is mechanical refusal in SovereignClaw?
Mechanical refusal means blocked operations have no execution path in the runtime. The adapter is structurally unreachable without a valid gate artifact. This is enforcement by architecture, not by filtering or heuristics.
What makes SovereignClaw enforceable for AI agent security?
SovereignClaw enforces 9 formal security properties through a deterministic Rust kernel. It treats LLM output as untrusted input, cryptographically gates every action, uses threshold signatures for elevated (T2) operations, and mechanically refuses sovereign (T3) operations under the default policy. Safety is enforced by architecture rather than by prompts, filters, or guardrails.