Change Data Capture Pipeline · View 06 of 21 · People and journeys
The trough is coverage, not cleverness
- Triage is fast when lag and as-of are published; it collapses when the table in question has no reconciliation verdict at all.
- So the architecture treats reconciliation coverage as an output: the set of tier-1 tables with a daily verdict is a reportable number (ADR-12).
What answers it
- Per-event lineage — source, table, log position, schema version, transform version — explains any single sink row.
- Repair is a replay to a shadow table and a swap, never correction SQL against the serving mirror (ADR-01, ADR-11).
Assumptions
- Row-count and sampled-checksum verdict per tier-1 table every 24 hours.
- Tier-1 is assumed to be 40 of the 180 replicated tables.