Make incremental movement loads include revised source rows

Project context

A fictional SaaS analyst reports expansion revenue differently from finance because snapshots, refunds and contract changes are joined at incompatible grains.

Setup prerequisites

• Create a synthetic source schema and local transformation project.
• Use integer minor units and distinct reporting currencies.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

• ADBT-101 · Declare the subscription-movement grain before joining invoice lines
• ADBT-103 · Reject source schema drift before materializing the mart
• ADBT-102 · Separate recurring contract value from collected cash
• ADBT-104 · Join customer segments as of the revenue event date

Acceptance criteria

• Track source revision or updated watermark with tie breaking.
• Recompute affected grain keys deterministically.
• Commit the output and checkpoint consistently.

Implementation constraints

• Document how deletions and corrections identify affected periods.

Verification to include

• Correct a prior end date and update the affected month.
• Retry after an interrupted run and avoid duplicate movement rows.

Deliverables

• Revision-aware incremental model

Rollout and recovery

Shadow full and incremental builds on a synthetic corpus; fall back to full rebuild if they diverge.

Value of the work

For the engineer: Practice analytical modeling and explainable transformation contracts.

For the team: Review trustworthy reporting definitions and the cost of correcting historical reports.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.