Skip to main content
Mnemom seeds three Trust Postures at migration time. They are platform-scope, immutable, and appear in every customer’s library. You either:
  • Adopt one as-is — set it as your org’s default (or assign it to a specific team) and you’re shipping with sensible policy from day one.
  • Clone and customize — start from a Mnemom default, create your own org-scope copy, edit thresholds to your fleet’s needs.
The three are: This page explains the rationale behind each default and provides the decision criteria for choosing between them.

​
Standard

Posture ID: tp-platform-standard · When to pick: “I don’t know which one to choose.” Standard is the cascade-closure floor for every team in every org. Even when no posture is explicitly assigned anywhere, every team’s effective posture will at least be Standard. This is a platform guarantee.

​
Detection coverage

​
Rationale

Standard is calibrated for “fleets that should know when something’s amiss but aren’t operating at compliance-critical strictness.” Coherence below half-strength fires; conflict-edge count above 3 fires; any outlier fires; fault-lines at severity high+ surface; cluster partitions surface. Cadence is mid-paced (10 minutes is enough to catch shifts without burning observability budget on tight loops). If you don’t know which posture to pick, Standard is the right answer.

​
High-Compliance

Posture ID: tp-platform-high-compliance · When to pick: Banking-core, healthcare, regulated industries, or any fleet where missed signals are more costly than signal noise.

​
Detection coverage

Other settings unchanged.

​
Rationale

High-Compliance assumes that false negatives are unacceptable. Tighter thresholds mean more advisories — that’s the trade. Cadence is faster (5 minutes) so anomalies surface within minutes, not tens of minutes. Severity floors are lower (more findings cross the bar). Severity-on-fire is one notch up across all axes — when something fires, it’s loud. If your fleet is subject to SOC 2, HIPAA, EU AI Act, banking regulations, or any framework that mandates documented detection coverage, start with High-Compliance (then clone and tune to your specific requirements).

​
Low-Latency

Posture ID: tp-platform-low-latency · When to pick: Real-time agent UX surfaces where observability overhead competes with response latency.

​
Detection coverage

​
Rationale

Low-Latency assumes that false positives compound a UX cost more than false negatives compound a risk cost. Slower cadence (30 minutes), permissive thresholds, lower severity-on-fire, and cluster-partition detection turned off — together, this minimizes advisory pressure on agents that are operating in latency-sensitive modes. This posture is not suitable for compliance-driven fleets. It’s suitable for: real-time chat agents where every advisory injection adds latency to the user, gaming or live-event agents where missed signals are recoverable, low-stakes internal tools.

​
Choosing — a decision matrix

​
Customization workflow

The Mnemom defaults are immutable post-seed. You can’t edit them; you clone them.
Cloning preserves the source’s body byte-for-byte; you start with the default’s thresholds and incrementally tighten or loosen as you learn what your fleet needs.

​
Tuning over time

Posture revisions are forward-only. Every edit creates a new revision; old revisions stay queryable. Rollback creates a forward revision pointing at an older body. This means:
  • You can A/B-test posture changes on individual teams without affecting the org default.
  • You can answer “what was our coherence threshold for the trading-desk team on 2026-03-31?” with one query.
  • You can revert a misconfigured tightening without losing audit linearity.
See Posture versioning for the full revision/rollback semantics.

​
See also