A
AvenaTerminal · Est. 2026
Architectural Commitment 10 · Self-Aware Limitations

What Avena does not know.

Most data vendors hide weakness. The IMF, ECB Financial Stability Review, and FT publish theirs. We do the same — daily, automatically, generated by the system from real telemetry. Coverage gaps, low-confidence zones, ingestion failures, and stale feeds are all flagged here before a customer has to find them.

If this page looks dishonestly empty, the cron is broken. If it looks suspiciously full, we are being honest about a young dataset. Either reading is more useful than a marketing page.

significant
0
active findings
moderate
0
active findings
minor
0
active findings
No active findings

The compiler ran clean on its last pass. Either we genuinely have no flagged limitations (rare and worth being suspicious of) or the daily cron has not yet run for this environment. Check back tomorrow.

How this page is generated

A cron job at 02:30 UTC daily walks four passes: per-country coverage counts vs threshold; failed cron runs in the last 24h; AVM confidence rolling-averaged by town over 30 days; and macro feed staleness vs schedule. Findings that no longer trigger are automatically resolved. The full compiler source lives at src/lib/limitations.ts and is reproducible from the event store.