Data Fabric · Data Quality
Bad data is quarantined, not explained afterwards
An agent acting on a broken partition produces a confident wrong answer, which is the most expensive failure mode we have. So the checks block the write and the serve, and the owner is paged.
Column checks
218
Passing
216
Warnings
1
portfolio_snapshots late at the open
Failing
1
creative_performance row count
Check families
Each one has a blocking consequence, not just an alert
All 7 datasets · portfolio_snapshots ran 4 min late during the open.
Producer PRs · A breaking field change fails the producer's build, not the consumer's night.
218 columns · Out-of-range risk bands quarantine the partition instead of serving it.
Hourly · creative_performance dropped 38% — a channel API changed its export.
Every new column · Unclassified columns are unreadable by agents by default.
Consumer impact right now
Which agents are degrading, and how they say so
portfolio_snapshots
14 consumers affected. Growth agents read yesterday's snapshot and label every number as of that timestamp in the UI, rather than presenting it as live.
creative_performance
6 consumers affected. Growth agents read yesterday's snapshot and label every number as of that timestamp in the UI, rather than presenting it as live.
Everything else
Five datasets passing their contracts; their consumers are running on live data with no degradation notice.