freshness

DE//AGENT currently lists 4 resources under freshness: 3 tutorials, 1 hook. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Declare a freshness SLA and compute worst-case lag from a schedule — via Express a freshness check as a metric and an alert
• Express staleness as a metric and write an alerting rule — via Express a freshness check as a metric and an alert
• Configure no-data handling so silence is an alert, not a pass — via Express a freshness check as a metric and an alert
• Name the four dimensions of data quality — freshness, completeness, validity, consistency — via Name the four dimensions of data quality
• Map each dimension to a concrete signal — SLA, null rate, range, uniqueness — via Name the four dimensions of data quality
• Rank failure modes by blast radius before writing any test — via Name the four dimensions of data quality
• Confirm a freshness breach from a schedule diff in minutes — via Incident drill: a broken upstream caught by freshness and lineage
• Walk upstream with get_lineage to find the source that slowed — via Incident drill: a broken upstream caught by freshness and lineage

1 more objectives live on the individual resource pages.

These resources map to stages: Observability (3), Data Quality (1). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Express a freshness check as a metric and an alert score 34.15 — beginner
2. Name the four dimensions of data quality score 34.15 — beginner
3. Incident drill: a broken upstream caught by freshness and lineage score 31.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Express a freshness check as a metric and an alert, Name the four dimensions of data quality.

Security-flagged entries: Incident drill: a broken upstream caught by freshness and lineage (2 flags), Freshness Pre-Merge Check (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Express a freshness check as a metric and an alert — The first hands-on of the series: declare a freshness SLA, express staleness as a metric, and write an alert rule — including what happens when no data arrives at all. Ends with th… details
• Name the four dimensions of data quality — Build the mental model before writing a single test: freshness, completeness, validity, consistency. See each dimension in a real registry artifact — the SLA part of a contract, th… details
• Incident drill: a broken upstream caught by freshness and lineage — The source job quietly changed from hourly to daily; the mart's 6h freshness SLA now fails by construction. Run the drill — confirm the breach from the diff, walk upstream with get… details
• Freshness Pre-Merge Check — Warn when a change would silently widen the freshness SLA of a source. details

Adjacent topics: tutorial (3 shared), observability (3 shared), sla (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.