Attach source lineage to every accepted scan
Support found a delivery scan that neither carrier recognizes. The normalized table contains no batch hash, row position, or parser version to trace its origin.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Data lineage · Schema evolution · Least privilege
Estimated field mix
- Data engineering80%
- Storage systems20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional delivery marketplace receives JSON batches from three carriers. One uses local timestamps, another retries whole batches, and a third corrects delivery scans. Customer support needs a stable timeline rather than the last payload received.
Setup prerequisites
- JSON schema validation
- SQL queries
- Event-time concepts
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Store batch hash, row position, carrier identity, receipt time, and parser version.
- Link normalized records to a bounded source artifact reference.
- Restrict artifact retrieval to ingest support permission.
Implementation constraints
- Use synthetic data; do not copy full payloads into logs.
Verification to include
- Trace two accepted rows to their exact source positions.
- Deny a tracking viewer direct source-artifact access.
Deliverables
- Lineage migration and trace example
Rollout and recovery
Populate new imports first and mark untraceable legacy rows explicitly.
Value of the work
For the engineer: Practice ingestion contracts, deduplication, event-time reconciliation, and replayable data repair.
For the team: Examine how an engineer preserves source lineage and handles bad partner data without losing valid business events.
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.