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
CLPI Enforcement
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.
Trust Recovery
When trust breaks, we diagnose why. Card gaps mean missing documentation — fix the card. Behavior gaps mean actual violations — fix the agent.
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.
Cryptographic Proofs
Every verdict is Ed25519-signed, hash-chained, and Merkle-tree included. SP1 zkVM STARK proofs are available for every verdict and sampled by default at 10% — selective to keep cost aligned with risk. Trust Ratings publish on Base L2 for independent verification.
How Mnemom compares.
The only platform combining pre-action enforcement, policy DSL, cryptographic proof, and a cross-tenant Mnemom AEGIS Managed Rules pipeline.
| Feature | Mnemom | Arize | Langfuse | LangSmith | Patronus | Galileo |
|---|---|---|---|---|---|---|
| Pre-action enforcement | ||||||
| Policy DSL | ||||||
| Predictive intelligence | ||||||
| Cryptographic proof | ||||||
| On-chain Trust Rating (Base L2) | ||||||
| Trust recovery | ||||||
| Cross-tenant AEGIS Managed Rules | ||||||
| Mutation-phase adversarial arena | ||||||
| Public STIX 2.1 IoC feed | ||||||
| Append-only signed audit chain |
EU AI Act Article 50 — mapped.
Every transparency obligation, covered. Compliance presets ship in the SDKs.
| Requirement | CLPI Feature |
|---|---|
| Transparency documentation | Alignment cards + integrity certificates |
| Audit trails | Immutable hash chains with Merkle proofs |
| Risk categorization | Five-component Trust Rating with drift detection |
| Compliance reporting | Exportable compliance bundles with cryptographic attestation |
| Real-time monitoring | Continuous integrity checks, not quarterly audits |
Deadline: 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 signed and audit-chainable — the regulator's question and Mnemom's answer share a primitive.
| Article | Requirement | How Mnemom answers |
|---|---|---|
| Article 10 | Data governance | Alignment Cards declare data boundaries; AIP back-door screening verifies every output against PII/PHI patterns; CLPI Phase 2 governs the card lifecycle and amendments. |
| Article 12 | Record-keeping | Every integrity checkpoint, Managed Rule promotion, and advisory publication is Ed25519-signed and append-only chained. CLPI Phase 4 anchors Trust Ratings on Base L2 for independent verification. |
| Annex IV | Technical documentation | Exportable compliance bundles — Alignment Cards, IntegrityCheckpoints, signed promotion envelopes, advisory chains — assembled from the same primitives the runtime uses. |
