Menu
CSA AARM Builders Registry — Status: Aligned

Measured against a written specification.
Not against a marketing claim.

Strix Governance is listed in the Cloud Security Alliance AARM Builders Registry — status: Aligned. One of 49 listed builders working toward the same execution-time governance bar.

The listing — verbatim
“Embedded governance kernel with execution tokens and tamper-evident audit trails.”

That is a precise description. It is also a public commitment — alignment is not a marketing claim, it is a written assertion measured against a specification, with conformance gates ahead of it. We intend to close those gates.

What AARM is

Autonomous Action Runtime Management.

AARM is the emerging CSA-led standard for how AI agents and autonomous systems should be governed — not in policy documents, not in post-hoc audits, but at the moment of execution. The Builders Registry is where teams building toward that standard go on the record.

The category is execution control for AI agents. Strix sits between agent intent and real-world side effects. Every governed action is evaluated in-flight and decided three ways — allow, deny, or intercept — before it executes. Every decision is recorded as signed, independently verifiable evidence.

Not a logging layer. Not a dashboard. Not a sidecar. The kernel is the execution path.

What “Aligned” means in registry terms

A status, not a certification.

Aligned — current

Measured against the spec

Strix's architecture and product surface are evaluated against AARM's written runtime-governance criteria. Public on the registry.

Conformant — next

Passes conformance gates

The next gate. Conformance means independently testable evidence that the system behaves to the specification. We are building toward this. Verifier output is part of the proof.

Certified — future

Third-party attested

The senior status. Reserved for systems whose conformance is audited by a CSA-approved third party. The bar is high; that is the point.

How Strix maps to the AARM bar

The primitives are public and verifiable.

AARM expectationStrix primitive
Runtime governance (not post-hoc audit)Kernel sits in the execution path. Mutation does not run until evaluation completes. Five-invariant model.
Execution tokens with bounded authoritySingle-use HMAC tokens. 5-minute default TTL. Atomic redemption (`updateMany WHERE status=ACTIVE AND redeemedAt IS NULL`). Replay rejected.
Tamper-evident audit trailEd25519-signed evidence, canonical 13-field payload, SHA-256 hash chain. Reordering any field invalidates the signature.
Independent verificationPublic JWKS at /.well-known/strix-jwks.json (RFC 7517). npx @strixgov/verifier validates with zero Strix tooling.
Fail-closed enforcementNo signing key, no execution for HIGH/CRITICAL capabilities. Boot-time invariant check. Production-required secrets validated at first use AND eagerly at startup.
Capability-scoped agent surfaceSigned capability manifests with read vs write scope separation and deny-by-default. See Governed MCP.
The kernel path — at a glance

Same diagram on every surface.

Strix execution control architecture — Agent to MCP wrapper to capability manifest to STRIX KERNEL to ALLOW/DENY/INTERCEPT to execution to signed evidence to public verification

Governance, proven.

Grateful to the CSA AARM Technical Working Group for the rigor — and to the builders being measured alongside us. The bar is high. That is the point.