Why
AIP and AAP produce rich alignment telemetry: integrity verdicts, concerns, verification results, coherence scores, drift alerts. But this data is only useful if it’s observable. This exporter bridges the gap between protocol output and your existing observability stack by mapping everything onto OpenTelemetry spans, events, and metrics.Three integration layers
Quick start
TypeScript
Python
Span hierarchy
Spans are created as children of the current active span viacontext.active():
Attributes reference
For the complete attributes and metrics reference, see OTel Attributes.aip.integrity_check — 31 attributes + 4 GenAI SemConv fields
mnemom.span.role (customer / verifier) is also set on some spans so you can filter
verifier-internal traffic out of per-provider SLOs.
All fields are duck-typed and optional-chained — a missing field is skipped rather than
throwing, so partial checkpoints still produce a valid (if sparser) span.
aap.verify_trace — 8 attributes
aap.check_coherence — 5 attributes
aap.detect_drift — 2 attributes
Metrics
9 metric instruments for aggregate monitoring:Sideband findings (Trust Posture detectors)
A separate recorder,recorder.recordSidebandFinding(finding), covers fleet-level sideband
detector firings (coherence, fault-line, fleet, drift — see Tuning Sideband
Detection) rather than per-turn AIP/AAP results. It emits a
safe_house.sideband.finding span carrying safe_house.sideband.source, .axis, .team_id,
.finding_count, .severity, and .pattern_type, with one span event per affected agent.
Dashboard templates
Pre-built dashboards are available in the aip-otel-exporter repository:- grafana-aip-overview.json — Fleet-wide integrity monitoring
- grafana-aip-detail.json — Per-agent deep-dive
- datadog-aip-overview.json — Datadog importable dashboard
Platform examples
Integration examples are available in the examples directory:Performance
Every recorder call (recordIntegrityCheck, recordVerification, recordCoherence,
recordDrift) and the Workers-adapter helpers (createOTLPSpan, serializeExportPayload) ship
with their own Vitest benchmark (npm run bench in the TypeScript package) — run it against your
own hardware and Node version for current numbers. All of them are attribute-mapping and JSON
serialization only (no network I/O), so the overhead they add on your hot path is sub-millisecond.
Design principles
- Duck-typed inputs — No hard dependency on AIP/AAP packages. Works with any compatible shape.
- Graceful degradation — Missing fields are silently skipped, never throws.
- Zero-overhead Workers — CF Workers adapter uses only
fetch()+crypto, no OTel SDK. - GenAI SIG forward-compat —
gen_ai.evaluation.*aliases for future OTel GenAI SIG alignment.
Standards alignment
The exporter follows OpenTelemetry Semantic Conventions for span naming and attribute structure. Forward-compatible aliases (gen_ai.evaluation.*) track
the emerging OTel GenAI SIG
conventions for AI/ML observability.
This exporter is part of the Mnemom trust plane:
- AIP — Agent Integrity Protocol (per-turn thinking analysis)
- AAP — Agent Alignment Protocol (behavioral verification)
- aip-otel-exporter — This package (observability bridge)