Warn when a table stops updating
A table that can quietly stop updating, given a check that warns instead of showing last week's numbers.
The ticket
Add a freshness check to a table so staleness raises instead of rendering quietly.
Acceptance criteria
- The check fails when the table is deliberately stalled
- The threshold matches the table's real update cadence
- It alerts an owner rather than only failing a job
- Downstream dashboards indicate staleness rather than showing old numbers as current
What lands as proof
A deliberately stalled table failing the check, which proves the alarm is wired rather than merely configured.
Why teams defer it
- A stale dashboard still renders, so nobody reports it as broken.
- Setting the threshold needs the real cadence, which is often different from the documented one.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add a freshness check to a table so staleness raises instead of rendering quietly. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means the check fails against a deliberately stalled table, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.