# CAIN HERMES — Competitive Forensics

For each system: what it does, what it does not do, where its trust boundary ends, and what HERMES adds. No claim
of superiority without evidence; no claim of patent novelty.

| System | Implements | Does not implement | HERMES difference |
|---|---|---|---|
| OPA / Rego | policy evaluation, policy-as-code | governance *coverage proof*; cross-target semantic preservation; deployment integrity | HERMES proves requirement→effect coverage and preserves intent across targets |
| Cedar | authorization language + evaluator | coverage graph; enforcement integrity; drift ladder | HERMES adds coverage/integrity/drift |
| Kubernetes policy (PSA, Gatekeeper) | admission control for pods | agent-intent semantics; effect coverage; evidence chain | HERMES is agent/effect oriented; K8s adapter is DESIGN |
| cloud IAM-style controls | authorization for APIs | cross-target intent preservation; enforcement liveness | HERMES composes IAM-style limits with agent governance |
| MCP gateways / MCP firewalls | tool-call mediation | coverage proof; semantic preservation; deployment integrity | HERMES governs *whether the enforcement covers the intent* |
| A2A governance systems | agent card / delegation | cross-org coverage; evidence independence | ATLAS + HERMES |
| NVIDIA OpenShell (runtime isolation) | sandboxed execution | governance coverage semantics | HERMES coverage proof; OpenShell adapter DESIGN |
| AI-BOM / SBOM systems | component inventory | governance dependency → impact sets; coverage | HERMES governance SBOM with authority/effect impact |
| runtime security platforms | runtime detection/response | intent→enforcement preservation proof | HERMES proves preservation, not just detection |
| CAVA / TRACE / assurance frameworks | runtime assurance concepts | cross-target semantic preservation + coverage certificate | HERMES's recomputed coverage certificate |
| `govc` (CAIN, existing) | source→IR→package for one fabric | cross-target coverage/integrity/drift | HERMES is the coverage/integrity layer above it |

## Defensible differentiation
TRANSACTION-SCOPED, CONTINUOUS, EVIDENCE-BASED, CROSS-ORGANIZATION ASSURANCE (ATLAS) **plus** INTENT→ENFORCEMENT
COVERAGE PROOF AND SEMANTIC PRESERVATION (HERMES).

## Honest limits
Most comparisons are architectural; no head-to-head benchmark against competitors was run. Kubernetes/cloud/OpenShell
adapters are DESIGN, not implemented.
