Mnemom LogoMnemom
Sign in
AI Agent Governance

Policy enforcement. Not just policy documentation.

Define governance rules in YAML. Enforce them at the gateway — before your agents act. Prove every decision with cryptography.

The shift from monitoring to enforcement.

Traditional Monitoring

1Agent acts
2Action is logged
3Alert fires (maybe)
4Human investigates

CLPI™ Enforcement

1Agent requests action
2Policy evaluated at gateway
3Allowed or blocked instantly
4Proof generated automatically

Five pillars of AI agent governance.

Card Lifecycle & Policy Intelligence — from policy definition to cryptographic proof.

Policy Language

Define governance rules in YAML. Human-readable. Machine-enforceable. Version-controlled alongside your code.

# mnemom-policy.yaml
version: 1
rules:
  - action: access_pii
    effect: deny
    unless:
      - role: data_processor
      - consent: explicit
  - action: external_api_call
    effect: allow
    require:
      - trust_rating: ">= 600"

Shared Evaluation Engine

Same policies, three enforcement points. Shift-left at CI/CD. Pre-action at the gateway. Post-hoc at the observer.

CI/CD — shift-left validation
Gateway — pre-action enforcement
Observer — post-hoc audit

Trust Recovery

When trust breaks, we diagnose why. Card gaps mean missing documentation — fix the card. Behavior gaps mean actual violations — fix the agent.

●Card gap: missing or outdated alignment card
●Behavior gap: agent violated declared policy

Predictive Intelligence

Fault line analysis identifies where your agent fleet is likely to fail next. Risk forecasting and auto-generated policy recommendations — before incidents happen.

Fault line analysis
Risk forecasting
Auto-generated recommendations

Cryptographic Proofs

Every verdict is Ed25519-signed, hash-chained, and included in a Merkle tree. When proofs are enabled for the agent, SP1 zkVM STARK proofs cover a sample of verdicts. Checkpoint Merkle roots are anchored on Base L2 about every six hours.

SP1 zkVM STARK proofs (sampled · on request)
On-chain Trust Rating registry (Base L2)
Offline signature checks

How Mnemom compares.

The only platform combining pre-action enforcement, policy DSL, cryptographic proof, and signed Mnemom AEGIS Managed Rules.

FeatureMnemomArizeLangfuseLangSmithPatronusGalileo
Pre-action enforcement
Yes
No
No
No
Partial
No
Policy DSL
Yes
No
No
No
No
No
Predictive intelligence
Yes
Partial
No
Partial
No
Partial
Cryptographic proof
Yes
No
No
No
No
No
On-chain Trust Rating (Base L2)
Yes
No
No
No
No
No
Trust recovery
Yes
No
No
No
No
No
Signed AEGIS Managed Rules
Yes
No
No
No
No
No
Append-only signed audit chain
Yes
No
No
No
No
No

EU AI Act Article 50 — mapped.

Every transparency obligation, covered. Compliance presets ship in the SDKs.

RequirementCLPI Feature
Transparency documentationAlignment cards + integrity certificates
Audit trailsSigned hash chains with Merkle proofs
Risk categorizationFive-component Trust Rating with drift detection
Compliance reportingExportable compliance bundles with cryptographic attestation
Real-time monitoringContinuous integrity checks, not quarterly audits

Applies from August 2, 2026. Compliance presets ship in the SDKs today.

EU AI Act — Articles 10, 12, and Annex IV mapped.

The full enforcement provisions, not just Article 50 transparency. Every governance event is audit-chainable; cryptographic signing applies to integrity checkpoints and Managed Rule promotions — the regulator's question and Mnemom's answer share a primitive.

ArticleRequirementHow Mnemom answers
Article 10Data governanceData boundaries are org-defined on the Protection Card's protected surface (assets, forbidden ops, escalation-required); Alignment Cards declare the agent's intent and autonomy bounds; AIP back-door screening verifies every output against PII/PHI patterns; CLPI Phase 2 governs the card lifecycle and amendments.
Article 12Record-keepingEvery integrity checkpoint and Managed Rule promotion is Ed25519-signed and append-only chained. Advisory publications are recorded to the same append-only audit trail. CLPI anchors checkpoint Merkle roots on Base L2 about every six hours.
Annex IVTechnical documentationPer-agent exports of integrity checkpoints with signatures and chain links, score history, card amendments and reclassifications. Any checkpoint certificate can be checked against Mnemom's published public keys.

Ready for governance that's more than a dashboard?