Risk Graphprototype

Data source registry

The tables, dashboards, and feeds your existing reporting already runs on — registered with owners and refresh expectations, so metrics get lineage and staleness gets caught.

SourceKindOwnerRefreshLast refreshedBound metricsStatus

auth_events (warehouse)

user_id, event, ip, asn, mfa_method, ts

tableData Engevery 1d2026-11-10

ATO attempts / 10k logins (RSK-014)

Successful ATO rate (RSK-014)

MFA adoption (RSK-014)

Privileged exports / week (RSK-033)

stale

Fraud ops board (Looker)

ato_flags, lockouts, churn_cohort

dashboardFraud Opsevery 1d2026-11-09

90-day churn of ATO'd accounts (RSK-014)

Mean time to lockout (RSK-014)

DSAR responses on time (RSK-041)

stale

Chargeback spreadsheet

month, disputes, chargeback_usd

manualFinanceevery 30d2026-09-24

Chargeback rate (RSK-052)

fresh

SDAT domain-risk API

domain, risk_score, aitm_flag

apiTrust & Safetyevery 1d2026-11-10nonestale

messaging_billing (warehouse)

account_id, route, segments, spend_usd

tableData Engevery 1d2026-11-10nonestale

A stale source doesn't just flag here — it cascades: every bound metric goes stale, the owning risk's blindness rises, and any report depending on it is blocked from issuance until resolved or annotated.