rollback

DE//AGENT currently lists 3 resources under rollback: 2 tutorials, 1 runbook. 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:

• Map replication and consistency from DDIA to mechanisms in your own stack — via DR and replication — design the recovery path before you need it
• Keep the old data until the new data is validated — shadow-then-swap as rollback — via DR and replication — design the recovery path before you need it
• Classify recovery per failure class — code rollback vs quarantine-then-retry vs recompute — via DR and replication — design the recovery path before you need it
• Contain the damage before diagnosing — rollback first — via When an agent does the wrong thing — contain, audit, postmortem
• Reconstruct what the agent did from the audit trail — via When an agent does the wrong thing — contain, audit, postmortem
• Produce a blameless postmortem with dated, owned action items — via When an agent does the wrong thing — contain, audit, postmortem

These resources map to stages: Reliability (1), Agentic Data Engineering (1), Cloud (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. DR and replication — design the recovery path before you need it score 34.15 — intermediate
2. When an agent does the wrong thing — contain, audit, postmortem score 34.15 — advanced
3. Bad deployment score 32.25 — intermediate

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

Reach for these with production experience: When an agent does the wrong thing — contain, audit, postmortem.

Security-flagged entries: Bad deployment (2 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

• DR and replication — design the recovery path before you need it — Disaster recovery for data systems starts before the outage: DDIA's replication and consistency chapters name the mechanisms, and the registry's runbooks name the recovery paths — … details
• When an agent does the wrong thing — contain, audit, postmortem — An agent merged a change it should not have. Roll back first, use the scoping you configured to contain and reconstruct what happened — diffs, logs and approve-once records — walk … details

Adjacent topics: tutorial (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.