Three fleet products. One question: is the behavior still the one you attested to ?
Every governed system carries a signed baseline — a drift bound it must live inside. The solid line is governed
behavior; the faint trace is where the raw system was headed. When they part at the rail, that gap is risk being held — live.
01
Drift bounds · live
composite drift index · 8 Hz trace · solid = governed · faint dash = ungoverned trajectory · band = attested ±2σ
Ambient Clinical Scribe
— baseline b-2291 · held 0
in bounds
Prior-Auth Copilot
— baseline b-2304 · held 0
re-attested
Claims Triage Agent
— baseline b-2287 · held 0
in bounds
02
Excursion & attestation ledger
every bound event is a signed receipt · cause per drift-state classifier
Event UTC System Magnitude Cause · classifier Resolution Receipt
03
Drift fingerprint · now
|z| vs attested bound, per dimension · ▲ = above bound
shade ∝ |z| (0 → 3σ) · values are current-window z-scores against each dimension's attested bound
04
Distribution shift · grounding score
last 24 h vs attested baseline · PSI flagged ≥ 0.20
05
Dimension instruments · fleet-wide
72 h · shaded band = attested envelope
06
Posture · 7 days
96.2%
Time in bounds · fleet
4.2 min
Mean time to detect
14 · 41,203 receipts
Baselines attested
Live synthetic telemetry, seeded generator — episodes recur continuously. Attestation hashes are computed
live in this browser (SHA-256, WebCrypto). Bounds and baselines are attested values :
they move only by signed re-attestation, never by silent recalibration. Drift-state cause classification per the
Glacis drift engine. · glacis.receipt.v1 · OVERT v1.1