Data lineage & pipeline health — every data stream, the path it travels from its outside source into the dashboard, and whether it is flowing, lagging, blocked, or dark. Read live from the database on every load.
Empty 1Dark 3Manual 1Live 5
Lineage flow
Stream table
Stream
Source
Cadence
Heartbeat
Covers
Rows
Panels
Status
ibkr_positions
Interactive Brokers
daily Mon-Sat
1d ago
2026-06-29
29
3
Live
ibkr_nav
Interactive Brokers
daily Mon-Sat
1d ago
2026-06-29
27
2
Live
news_feed
Mimir research
continuous
just now
2026-07-01
15.939
2
Live
research_feed
Mimir research
daily
just now
2026-07-01
188
1
Live
conviction
Broker research
daily
just now
2026-07-01
212
2
Live
fx_isk
Central Bank of Iceland
daily
—
—
0
2
Empty
isk_nav
Manual (fund ops)
manual
—
2026-05-29
15
2
Manual
allocation
Interactive Brokers
daily
—
—
26
2
Dark
benchmark
Public rate sources
daily
—
—
12
1
Dark
monthly_pnl
Interactive Brokers
monthly
—
—
9
1
Dark
How to read this
BlockedThe last pipeline run failed — data is not advancing until it is fixed.
StaleHas data, but the pipeline has not fired within its expected window.
EmptyProducer is wired but no rows have arrived yet — not yet flowing.
DarkData is in the database, but no panel or heartbeat is wired to it yet. A roadmap signal, not a failure.
ManualOperator-entered — there is no automated producer for this stream.
LiveFlowing — pipeline fired within its cadence and rows are present.
Two clocks. The heartbeat is when the pipeline last fired; it drives the status. The data date ("covers through") is the date the data actually reflects. For Interactive Brokers these differ by one day by design — the pull runs today and delivers yesterday's settled statement — so a one-day gap is not staleness.
Static preview of the /kerfi React page, populated with the ViskaDB schematic §11 proven live-state snapshot (2026-07-01). The shipped page reads public.v_data_lineage_health live. ViskaFront · dispatch 016.