sla

DE//AGENT currently lists 8 resources under sla: 5 tutorials, 1 skill, 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.

Also present: 1 runbook.

Documented learning objectives across these resources:

• Specify a freshness and completeness SLA — via Data Contract Author
• Encode a contract as executable tests — via Data Contract Author
• Define a breaking-change policy consumers can rely on — via Data Contract Author
• Write all six parts of a contract for a real dataset — via Author your first data contract
• Specify freshness and completeness numbers in the SLA — via Author your first data contract
• Name the CI test that fails when the contract is violated — via Author your first data contract
• 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

10 more objectives live on the individual resource pages.

These resources map to stages: Data Quality (4), Observability (3), Reliability (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. Data Contract Author score 38.5 — intermediate
2. Author your first data contract score 34.15 — beginner
3. Express a freshness check as a metric and an alert score 34.15 — beginner

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

Start here if you're new: Author your first data contract, Express a freshness check as a metric and an alert, The data reliability mental model — freshness, completeness, correctness.

Security-flagged entries: Data Contract Author (1 flag), Data contract broken (2 flags), Production gotchas: alert fatigue, missing contracts, no-data silence (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.

• Data Contract Author — Drafts a data contract (schema, semantics, freshness SLA, ownership, breaking- change policy) and the tests that enforce it in CI. details
• Author your first data contract — Draft an enforceable contract for one real dataset by walking the six parts — owner, schema, semantics, SLA, breaking-change policy, enforcement — starting from the data-contract t… details
• 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
• The data reliability mental model — freshness, completeness, correctness — Build the map before writing a single check: a consumer experiences a table as three properties — freshness, completeness, correctness — declared as an SLA in a data contract, enfo… details

Real install commands from the registry — read the source before running any of them:

npx de-agent-platform add data-contract-author

Data Contract Author — review first

Adjacent topics: tutorial (5 shared), observability (3 shared), beginner (2 shared), freshness (2 shared), data-contract (2 shared), alerting (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.