Environments drift — vendors patch, engineers tweak, exceptions accumulate. Panaptico reconciles the live state against the implementation graph every minute and surfaces the changes that matter, attributed to who or what made them.
sp · finance-etl-prod
Azure
sensor policy · EMEA-finance
CrowdStrike
group · fin-admins
Okta
warehouse · REPORTING_WH
Snowflake
kms key rotation · 14 CMKs
AWS
monitor · auth-latency-p99
Datadog
policy · pki-intermediate
Vault
integration system user
Workday
3 critical · 3 notable · 2 expected · every row linked back to intent and attribution
DRIFT-FEED-0491 · liveWhy existing monitoring misses it
01
Datadog tells you latency jumped. Nobody tells you the warehouse was resized to L an hour ago, and nobody approved it. The alert and the cause live in two different tools.
02
The cloud trail logs 40,000 changes a day. Nine out of ten are routine. The one that matters is buried in noise. Humans give up; the tenth one becomes an incident.
03
Who changed the CrowdStrike policy to monitor-only? The console shows a service-principal name that wasn't tied to a human. Two weeks later, nobody admits to it.
Continuous reconciliation
The implementation graph is the anchor. Every connector syncs the live state on a loop and Panaptico computes the delta — per object, per field, with the reason-of-record when there is one.
Intent · graph anchor
Live · observed
Fields checked
92,418
Drifted
217
Attributed
203
Unknown source
14
Smart classification
Raw state transitions get classified against the implementation graph — scoped, explained, and routed by impact. You see the 14 that matter, not the 18,417 that don't.
The funnel turns 18k events into a queue of 14 — each one with context, not a ticket template
Object
azure · finance-etl-prod · service principal
Change
Why it's critical
Change attribution
Each drift gets correlated against the graph's source streams — CHG tickets, Terraform runs, vendor patch feeds, SCIM syncs, human console activity. "Unknown source" is a category, not a shrug.
Terraform Cloud · workspace finance-prod
run #2841 · plan applied 14:21:08Z
Snowflake activity log · user
session held by svc-dbt-prod · no interactive user
CHG ticket queue
no ticket matched object · window ±60min
Vendor patch feed
no Snowflake release event in window
Attributed to Terraform run #2841 · commit a4f2…e991 · author j.tran@ · auto-linked to CHG-00604
Automated response
Every classified drift gets routed automatically — re-baselined, turned into work, sent back through approval, or escalated. Humans approve policies, not individual alerts.
When
drift is expected · matches vendor patch feed or scheduled change
Action
auto-rebaseline · write to graph · no human in the loop
Volume
8,902 in last 24h
When
drift is notable · bounded deviation inside policy envelope
Action
generate TASK · assign owner · require CHG within 7 days
Volume
389 in last 24h
When
drift touches a signed decision record · must re-approve
Action
open approval · attach DR · route to original approver
Volume
11 in last 24h
When
drift breaks an intent contract or has no attributable source
Action
freeze object · page oncall · capture forensic bundle
Volume
3 in last 24h
Rules are reviewed quarterly · every auto-action is written back into the graph as an attributed event
ROUTING-POLICY-v14The environment is always changing. Panaptico keeps the graph honest — every change classified, every cause linked, every response written back.