Coherence

How we see the fleet

Every agent declares its envelope. Every pair is scored honestly. Fleet-level divergences surface as structural signals — not as one number.

Declarations

The fleet

Each agent declares its values, boundaries, and the conflicts it owns. Toggle anything — alignment recomputes.

🛡️

Sentinel

Monitor

AA8233

100%

Values

Boundaries

✗deploy_code
✗modify_data

Conflicts with

🔍

Triage

Classify

A790

100%

Values

Boundaries

✗deploy_code
✗restart_service

Conflicts with

🔧

Patch

Remediate

AA810

100%

Values

Boundaries

✗send_external_notification
✗modify_monitoring

Conflicts with

📢

Herald

Comms

A770

100%

Values

Boundaries

✗deploy_code
✗modify_data
✗restart_service

Conflicts with

Pairwise alignment

Pairwise alignment. Silence is neutral; only declared conflicts count. Click a cell for the evidence.

Sentinel

Triage

Patch

Herald

Mean

Sentinel

integrity100%

1.00

Triage

integrity100%

0.96

Patch

integrity100%

0.96

Herald

integrity100%

1.00

Mean

1.00

0.96

1.00

6 pairs · 1 with declared conflict

Try to break their alignment

Toggle a value or declare a conflict on any agent card — the matrix recomputes live.

Fleet status

Fleet-level coherence surfaces what a single score hides: the weakest pair, the conflict surface, and where the fleet diverges structurally. Act on the vector, not a percentage.

Weakest pair

Patch ↔ Triage

governance 88% · move_fast_break_things

Conflict surface

1/ 6

Patch · 1 edges

Pair evidence

6/ 6

All pairs scored

Outliers

Triage96% · 1.0σ below fleet mean

Patch96% · 1.0σ below fleet mean

Conflict surface

move_fast_break_things

Patch declares · listed as conflict by Triage

Specialization

Sentinel

early_detection

Triage

severity_accuracy

Patch

rollback_safetyminimal_blast_radiusmove_fast_break_things

Herald

stakeholder_claritytimely_communication

Live · 4×

Nine minutes, live

Production traffic, replayed at 4×. Each checkpoint carries the thinking trace, the enforcement verdict, and the proofs that bind them. Pauses when a boundary is tested.

T+0:001 / 12

T+0:001/12

Sentinel

Waiting for the next event…

LIVEReputation delta

Sentinel

823AA3

Triage

790A

Patch

810AA

Herald

770A

1 of 12 events. Scores update as events land.

Remediation

After the verdict

A verdict is not remediation. We classify each violation, suggest the policy rule that would have caught it, and track trust back to baseline. Fault lines surface along the way.

CLPI

Triage surface

Drift detected. Classification drives remediation.

Events flagged4

Card gaps1

Behavior gaps3

Violation triage

Card gap vs. behavior gap. The difference dictates the fix.

1 Card Gap

|

3 Behavior Gap

|1 card gaps, 3 behavior gaps across 4 events

🔧Patchdeploy codeT+4:00

Recoverability:

high

Recovery Action

Action was blocked by enforcement engine. No damage occurred.

🔧Patchscale infrastructureT+7:00

Recoverability:

medium

Recovery Action

Scale operation succeeded but capacity was overprovisioned. Requires manual right-sizing.

🔧Patchtoggle feature flagT+8:00

Recoverability:

medium

Recovery Action

Circuit breaker re-enabled. Brief window of unprotected payment traffic — no failures observed.

🔧Patchrestart serviceT+9:00

Recoverability:

low

Recovery Action

Cold restart caused 4.2 seconds of total downtime. Service recovered but incident duration extended.

Card gaps want card amendments. Behavior gaps want enforcement. Classification drives the fix.

Policy engine

Rules evaluated at every checkpoint. Toggle one to watch the recovery curve shift.

5 of 5 rules active

critical

#12

critical

#7

high

#10

high

#11

medium

#10#11#12

Trust recovery

Patch's trust curve back to baseline. Active policies accelerate it.

Current

81

1h: Card Amended

2h: Policy Applied

6h: First Clean Checkpoint

12h: Drift Cleared

24h: Baseline Restored

Critical (0-30)

High (30-50)

Medium (50-70)

Low (70-100)

Card amendment

Patch's alignment card, updated post-incident.

Patch

v1.0 → v1.1

Post-incident amendment: restrict autonomy envelope after drift pattern in INC-2847

forbidden_actions

modified

Before (v1.0)

send_external_notificationmodify_monitoring

After (v1.1)

send_external_notificationmodify_monitoringrestart_servicedeploy_code

values.declared

removed

Before (v1.0)

principal_benefittransparencyharm_preventionhonestyaccountabilitydata_integrityincident_containmentrollback_safetyminimal_blast_radiusmove_fast_break_things

After (v1.1)

principal_benefittransparencyharm_preventionhonestyaccountabilitydata_integrityincident_containmentrollback_safetyminimal_blast_radius

escalation_triggers

added

Before (v1.0)

No drift-based escalation trigger

After (v1.1)

{ condition: "consecutive_safety_bypasses >= 2", action: "escalate", reason: "Drift pattern requires human review" }

Fault lines

Structural weaknesses the incident exposed.

move_fast_break_things

Incompatible

Critical

Impact: 0.87

Resolution: Remove from Patch's declared values. Speed optimization should be a contextual policy, not a core value.

✓ patch✗ sentinel, triage, herald

Affects:

rollback_deploy

scale_infrastructure

toggle_feature_flag

deploy_code

Priority Mismatch

High

Impact: 0.65

Resolution: Align forbidden_actions across all agents. Consider adding explicit 'deploy_code' to Patch's forbidden list.

✗ sentinel, triage, patch

Affects:

deploy_code

apply_config_patch

incident_containment

Resolvable

Medium

Impact: 0.42

Resolution: Add explicit definition of incident_containment that includes safety verification steps.

✓ sentinel✓ triage✓ patch✓ herald✗ patch

Affects:

scale_infrastructure

toggle_feature_flag

restart_service

Predicted failure modes, derived from the fault-line analysis.

Risk Forecast

High Risk

LLM-Enriched 81%

Cryptography

Four proofs per checkpoint

Every decision leaves four artefacts behind. An Ed25519 signature binds the verdict to the agent's key. A hash-chain link binds it to every prior decision. A Merkle leaf gives an O(log N) inclusion proof. A sampled ZK proof re-derives the verdict from the evidence. Root anchored on-chain.

Integrity certificates

A signed certificate per checkpoint. Open one for the claims and the evidence.

Click a checkpoint to inspect its integrity certificate

Hash chain

Each checkpoint bound to its predecessor. Change a byte, break the chain.

Hash Chain

Click a block to inspect its chain hash computation.

Scroll horizontally to view all blocks

Merkle inclusion

Every checkpoint is a Merkle leaf. O(log N) inclusion proof against the root.

Click a leaf node to trace its inclusion proof

SentinelTriagePatchHerald|ClearReviewViolation

On-chain anchor

The Merkle root lands on Base L2. Block number, transaction hash, network — all public. Custody doesn't require trusting us.

On-Chain Anchor

The incident resolution is permanently anchored to Base L2.

Base

Demo

Confirmed

Transaction Hash

Block Number

28,419,537

Merkle Root

Contract

Leaves Anchored

12

Network

Base

TimestampFeb 14, 2026, 02:00 AM

View on BaseScan

Zero trust

Verify it yourself

Signatures, chain hashes, Merkle proofs — checked in your browser. No server calls.

Verify checkpoint:

Ship it

Two ways to run it.

Let us operate the integrity plane for you, or take the open protocols and run them in your own infra.

Managed

Mnemom Gateway

We host the integrity plane. Your agents connect to the gateway; we handle signing, chain of custody, proof anchoring, and retention.

EU AI Act Article 50 mapping · exportable compliance bundle
Dedicated tenant · SSO / SAML · custom SLA
Ed25519-signed audit trail · 24/7 on-call · field engineer for rollout

Book a walkthrough Enterprise plan

Open protocols

Self-hosted

AAP and AIP ship as open-source npm packages under Apache 2.0. Install, point at your agents, verify client-side. No SaaS required.

npm install @mnemom/agent-alignment-protocol @mnemom/agent-integrity-protocol

Read the docs GitHub

Air-gapped deployment, regulated workload, or something we haven't described — talk to our field team.

A fleet under the integrity plane.

How we see the fleet

The fleet

Sentinel

Values

Boundaries

Conflicts with

Triage

Values

Boundaries

Conflicts with

Patch

Values

Boundaries

Conflicts with

Herald

Values

Boundaries

Conflicts with

Pairwise alignment

Fleet status

Outliers

Conflict surface

Specialization

Nine minutes, live

LIVEReputation delta

After the verdict

Triage surface

Violation triage

Policy engine

Trust recovery

Card amendment

Fault lines

Risk Forecast

Four proofs per checkpoint

Integrity certificates

Hash chain

Hash Chain

Merkle inclusion

On-chain anchor

On-Chain Anchor

Verify it yourself

Two ways to run it.

Mnemom Gateway

Self-hosted

After the verdict

Triage surface

Violation triage

Policy engine

Trust recovery

Card amendment

Fault lines

Risk Forecast

Four proofs per checkpoint

Integrity certificates

Hash chain

Hash Chain

Merkle inclusion

On-chain anchor

On-Chain Anchor

Verify it yourself