SYSTEM HEALTH
every feed, every worker, every API — because a signal built on stale data is worse than no signal. Data Confidence scores on the Board come straight from this page.—System Trust Score. One number: freshness × completeness × latency across all feeds. When this drops below 85 the header beacon turns amber everywhere; below 70 the Board watermarks affected strips and squawk announces it. You will never unknowingly trade on bad data.
Data Sourceslive · from worker heartbeats
Waiting for worker heartbeats — sources report in every scan cycle.
Incidents — recentauto-detected · auto-resolved when clear
No active incidents. Feed slowdowns, worker restarts, and API failures appear here with their impact and auto-resolution status.—
What happens when a feed breaks
The system degrades honestly instead of pretending:
• Affected strips get a ⚠ stale-data watermark and Data Confidence drops on the score breakdown
• Models that depend on the dead feed (Sweep Cluster without flow) pause and say so — no guessing
• Models that don't need it (ORB-F on price/volume) keep running at full trust
• Squawk announces it once: "Flow feed degraded — flow models paused"
• Telegram ping to you if it lasts > 5 minutes
• Everything auto-resumes and backfills when the feed returns
• Affected strips get a ⚠ stale-data watermark and Data Confidence drops on the score breakdown
• Models that depend on the dead feed (Sweep Cluster without flow) pause and say so — no guessing
• Models that don't need it (ORB-F on price/volume) keep running at full trust
• Squawk announces it once: "Flow feed degraded — flow models paused"
• Telegram ping to you if it lasts > 5 minutes
• Everything auto-resumes and backfills when the feed returns