reliability

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

• Write a blameless timeline — via Incident Postmortem Writer
• Separate trigger from contributing factors — via Incident Postmortem Writer
• Convert findings into dated, owned action items — via Incident Postmortem Writer
• Name the three properties a consumer experiences — freshness, completeness, correctness — via The data reliability mental model — freshness, completeness, correctness
• Read a data contract's SLA section as the table's reliability promise — via The data reliability mental model — freshness, completeness, correctness
• Explain why an unenforced SLA is documentation, not a contract — via The data reliability mental model — freshness, completeness, correctness
• Run the reliability checklist over your own pipeline end to end — via Capstone — the reliability checklist for a pipeline you can page on
• Drill the incident path — match the alert, walk the runbook, capture the timeline — via Capstone — the reliability checklist for a pipeline you can page on

19 more objectives live on the individual resource pages.

These resources map to stages: Reliability (7), System Design (3). 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. Incident Postmortem Writer score 38.9 — beginner
2. The data reliability mental model — freshness, completeness, correctness score 34.15 — beginner
3. Capstone — the reliability checklist for a pipeline you can page on score 34.15 — intermediate

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

Start here if you're new: Incident Postmortem Writer, The data reliability mental model — freshness, completeness, correctness.

Security-flagged entries: Incident Postmortem Writer (1 flag). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• Incident Postmortem Writer — Structures incident notes into a blameless postmortem: timeline, impact, detection gap, contributing factors, and action items with owners and dates. 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
• Capstone — the reliability checklist for a pipeline you can page on — Close the series by running the reliability checklist over your own pipeline: a declared and enforced SLA, idempotent tasks with backoff retries, a documented backfill runbook — th… details
• Define reliability in numbers — SLIs, SLOs, and error budgets — A design without reliability numbers is a wish. This lesson borrows the SRE toolkit — SLIs, SLOs, error budgets, incident management, postmortems, and capacity planning — and point… details

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

npx de-agent-platform add incident-postmortem-writer

Incident Postmortem Writer — review first

Adjacent topics: tutorial (8 shared), sre (3 shared), incident (2 shared), production (2 shared), system-design (2 shared), postmortem (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.