CIRIS has a new look. Visit the new site →

back to the lobby

Comparison, fixed criteria

CIRIS vs the Microsoft Agent Governance Toolkit

Two serious open-source attempts to govern AI agents, scored on the same eight criteria from public sources, with a citation on every cell. Where Microsoft is strong, we say so. The differences that matter are shipping, an enforced constitution you cannot loosen, and post-quantum signed records.

CriterionCIRISMicrosoft Agent Governance Toolkit
Enforces policy before the action runsYesYes
Signed, tamper-evident decision recordsYesPartial
Cryptographic agent identityYesYes
Kill switch / revoke a rogue agentYesPartial
Published, enforced constitutionYesPartial
Independent third-party verificationPartialPartial
Open sourceYesYes
Shipping in productionYesPartial

Scored from public product docs as of July 2026. If we have a cell wrong, tell us and we will fix it.

Sources
  1. Enforces policy before the action runsCIRIS: CIRISAgent conscience_execution.py (H3ERE runtime gate) · Microsoft: Agent Control Specification (8 intervention points)
  2. Signed, tamper-evident decision recordsCIRIS: CIRISAgent audit (hash-chained + PQC-signed), CIRISConformance test_320 · Microsoft: ADR-0017 Merkle Audit Chain (spec; signing not confirmed in public docs)
  3. Cryptographic agent identityCIRIS: CIRISVerify hybrid Ed25519 + ML-DSA-65, 2-of-3 multi-source · Microsoft: Agent Mesh DID identity (Ed25519) + Entra Agent ID
  4. Kill switch / revoke a rogue agentCIRIS: CIRISVerify HUMANITY_ACCORD (fail-secure 2-of-3 named-human quorum) · Microsoft: Agent SRE emergency termination + Entra identity disable (reversible)
  5. Published, enforced constitutionCIRIS: CIRISConstitution (CC 0.4) binds every action; enforced via the conformance suite · Microsoft: Operator-authored YAML/Rego/Cedar policy; documented default_action: allow (ADR-0006)
  6. Independent third-party verificationCIRIS: Verifiable by design (walk the signed log) + conformance suite; external audits as needed · Microsoft: OpenSSF Scorecard / Best Practices badges (supply-chain hygiene, not decision verification)
  7. Open sourceCIRIS: AGPL-3.0 (network copyleft): CIRISAgent, CIRISVerify, CIRISConformance · Microsoft: MIT: microsoft/agent-governance-toolkit
  8. Shipping in productionCIRIS: CIRIS app on Apple App Store + Google Play today · Microsoft: Toolkit README: "Public Preview" (not yet GA)

Microsoft's real strengths

The Agent Control Specification is a genuine stateless, deterministic, fail-closed policy runtime with eight named intervention points and a five-way verdict model (allow, warn, deny, escalate, transform). It ships DID-based Ed25519 identity, an emergency kill switch, and strong open-source engineering under a permissive MIT license, with deep Azure and Entra integration for enterprises.

Where CIRIS goes further

Every action passes a runtime conscience pipeline before it executes, not a post-hoc log. The audit trail is hash-chained and post-quantum signed, and independently re-verified by a separate conformance suite. The kill switch is a fail-secure two-of-three named-human quorum. And the constitution is fixed and published, not an operator-authored policy that defaults to allow.

This is one row of a bigger picture. See where both sit among every approach to AI accountability.

CIRISsafe by structure · open by principle · kind by design