How to read freshness badges
Lankawa compares the last successful fetch time against each source's expected update cadence. Badges appear on pulse cards, source pages, and the status dashboard.
What you see on Lankawa
The badge on a metric tells you how recently we confirmed the upstream source — not whether the underlying event happened.
Sample pulse metric
302.45 LKR
FreshAs of last successful fetch · illustrative
Fetched within the expected cadence for this source.
Good default for daily checks.
Older than expected — upstream may be delayed or cached.
Use for context; verify if timing matters.
Source unreachable on last check.
Open /status or the source page before relying on the number.
What this means
Fresh: the source responded within its expected cadence (for example, CBSL FX within roughly a business day, flood levels within about ten minutes to an hour depending on upstream).
Stale: data is older than expected but still available. Useful for context — verify before time-sensitive decisions.
Down: the adapter failed or the upstream API is unreachable. Check /status for the last error and whether a fallback is in use.
Badges describe our pipeline health, not official urgency levels. A Fresh flood reading can still be alarming; a Stale FX rate may still be the latest CBSL table.
What we will not claim
Fresh does not mean "correct for every use case" — only that the source responded recently. Down means we could not reach the source; we may show a cached or seed fallback elsewhere with clear labelling.