backfill

DE//AGENT currently lists 9 resources under backfill: 4 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 agent, 1 runbook, 1 pattern.

Documented learning objectives across these resources:

• Scope a backfill by date and by dependency — via Backfill Planner
• Detect which downstream tables must also be rebuilt — via Backfill Planner
• Stage a backfill gradually with validation between batches — via Backfill Planner
• Map one task over many date batches with dynamic task mapping — via Fan out over date batches with dynamic task mapping
• Scope the fan-out by date and by dependency — via Fan out over date batches with dynamic task mapping
• Validate a sample after each batch before continuing — via Fan out over date batches with dynamic task mapping
• Install a pre-run gate that intercepts backfill triggers — via Gate backfills with the safety check hook
• State the three requirements the hook enforces before any backfill — via Gate backfills with the safety check hook

7 more objectives live on the individual resource pages.

These resources map to stages: Orchestration (8), 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. Backfill Planner score 39.5 — advanced
2. Safe Backfill score 34.75 — advanced
3. Fan out over date batches with dynamic task mapping score 34.15 — intermediate

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

Reach for these with production experience: Backfill Planner, Safe Backfill, Backfill Safety Check.

Security-flagged entries: Backfill Planner (1 flag), Backfill required (3 flags), Backfill Planner (3 flags). Flags mean the record declares capabilities like credential use or write access — read the security posture on each page before connecting.

Known limits: A tiny table you can recompute in one safe step (Safe Backfill)

• Backfill Planner — Produces a backfill plan: date ranges, blast radius, resource contention, idempotency check, validation gates and rollback. details
• Fan out over date batches with dynamic task mapping — Run one task definition over many date batches with dynamic task mapping — the docs' mapping feature applied the way the backfill material demands: batched ranges, smallest first, … details
• Gate backfills with the safety check hook — Wire the Backfill Safety Check as a pre-run gate that refuses any backfill lacking an explicit date range, a shadow or snapshotted target, and a window clear of the scheduled produ… details
• Plan and execute a backfill that doesn't break production — Historical output is wrong or missing, and the fix touches a production table: define correct first, map the blast radius from lineage, then shadow-write in date batches smallest-f… details

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

npx de-agent-platform add backfill-planner

Backfill Planner — review first

Adjacent topics: safety (5 shared), tutorial (4 shared), orchestration (3 shared), planning (3 shared), hook (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.