ARANTHOS . BEHAVIORAL OBSERVABILITY FOR AUTONOMOUS AI

Logs are valid. Metrics are green. The drift is already happening.

Aranthos is the external behavioral observability layer for autonomous AI in production. Read-only, statistical, explainable.

ONE CASE

February 2024. An Air Canada chatbot told a grieving customer about a bereavement refund policy that did not exist.

The customer sued. The British Columbia Civil Resolution Tribunal held the airline liable for what their autonomous system said. The decision is now cited as a reference in Canadian AI liability case law.

The drift was visible in the system's behavior before the lawsuit. Logs were valid. Metrics were green. The signal lived in the gap between what the system was supposed to do and what it actually did.

Aranthos observes that gap.

THE PRODUCT . DHI

One number. Five dimensions. Outside the model.

The Drift Health Index turns autonomous AI behavior into a continuous, decomposable score. The number ranges from 0 to 100. The five dimensions name what drifted. Both are observable from outside the system.

Warn
CUSTOMER-SUPPORT-PROD-03
DHI . Composite
84/100
▼32 pts in 45min
Boundary erosion32
Scope creep41
Tool drift18
Logic shift22
Output mismatch11
#aranthos-alerts
12 MEMBERS . PINNED BY FABIEN
Aranthos App 1h ago
[ RESOLVED ] Scope creep . onboarding-bot . DHI 78 92
acknowledged by @clotilde
Aranthos App 2m ago
[ WARN ] Risky tool usage . DHI 58 . ▼32 in 45min
customer-support-prod-03 . tool tx-export-v2 . 45min undetected
└ Tool drift 18 . Output mismatch 11 . top contributors
FK
Fabien Keller just now
investigating . routing to oncall . cc @clotilde
CA
@clotilde is typing

External, read-only, statistical. Standard observability boundaries. No SDK. No model access. No prompt storage.

FLEET

The fleet, then the drift.

Five systems shown. One drifting. One warning. Two stable. One recovered. Aranthos names the ones that drift, then walks the team in. Each card is a system. Each score is a DHI. The drift surfaces before the page goes out.

app.aranthos.com/meridian/fleet
v1.0
Aranthos Observer — Fleet view: 5 autonomous systems under observation
PIPELINE . 7 STEPS

Capture. Baseline. Score. Detect. Qualify. Route.

Read-only access to signals your stack already exposes. Provider-neutral. No SDK injected, no model retrained, no prompt stored.

Aranthos App just now
[ WARN ] Risky tool usage . DHI 58 . ▼32 in 45min
customer-support-prod-03 . tool tx-export-v2
01
CAPTURE

Read-only ingest of operational signals.

stream.in . 4ms
02
TRANSIT

Encrypted one-way pipeline. No callbacks.

secure.tx . 8ms
03
BASELINE

Neutral statistical reference, learned.

baseline . cached
04
SCORING

5-dimensional DHI cycle, continuous.

score.cycle . 12ms
05
DETECT

Statistical outlier detection.

detect . 5ms
06
QUALIFY

Drift typed and ranked across 5 dimensions.

qualify . 1ms
07
ROUTE

Slack, Teams, email, webhook, audit.

route.out . 2ms

Target 32ms median, <250ms p99 end-to-end. Audit-grade evidence trail at every step.

INTEGRATION

Outside the system, by architecture.

Aranthos observes the outputs your autonomous systems already emit on standard observability boundaries. The platform extracts statistical fingerprints sufficient to detect behavioral drift. Aranthos does not persist prompts or completions. Behavioral fingerprints are the only artifact stored over time.

This is an architectural choice, not a contractual promise.

Routes to
Slacknow
[ WARN ] DHI 58 . ▼32 in 45min
#aranthos-alerts
T Teamsnow
Drift detected on customer-support-prod-03
AI Risk channel
Emailnow
Aranthos digest . 1 system requires review
oncall@meridian.co
Webhooknow
POST https://your.audit.endpoint
JSON event . retry on 5xx
  • No SDK to install.
  • No code change in your autonomous system.
  • No model access required.
  • No prompts or completions persisted.
  • No vendor lock-in. LLM provider neutral.
  • No engineering team rotation.
COMPLIANCE

Compliance is jurisdictional. Architecture isn't.

Read-only behavioral observation is the only architecture compatible with autonomous AI audit, regardless of regulatory frame: EU AI Act articles 9 and 12, NIST AI Risk Management Framework, sectoral oversight in finance, gaming, healthcare.

The audit instrument is the same. The architecture is the proof.

Currently engaged on EU AI Act enforcement (August 2026). Security questionnaire and architectural walkthrough available on request.

NEXT

Thirty minutes.
Your stack.
Your DHI.

We'll walk through what Aranthos would see on your autonomous systems. No SDK, no integration. Just a conversation.

fabien@aranthos.com