Produce a stock drift report before applying corrections
Operations sees different stock in the vendor portal and local app but has no item-level comparison. Add a read-only report against a completed synthetic snapshot.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Reconciliation · Reporting · Data comparison
Estimated field mix
- Integrations60%
- Data engineering40%
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 retailer receives stock from two vendor warehouses. The vendor API paginates snapshots and emits change events, but retries and deleted products have caused unexplained stock drift. Work against a local vendor simulator.
Setup prerequisites
- Create a local vendor API simulator with cursor pages and stock events.
- Use synthetic tenants, SKUs, and warehouse records; no vendor account is required.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- The report lists local quantity, vendor quantity, revision, warehouse, and difference for each mapped item.
- Equal items can be hidden without changing discrepancy totals.
- Unmapped items and incomplete snapshots are labeled separately from confirmed quantity drift.
Implementation constraints
- Include tenant and connector labels only within authorized operator scope.
Verification to include
- Compare a fixture with one equal, one mismatched, and one unmapped item.
- Attempt a report from an incomplete snapshot and verify no discrepancy is presented as a confirmed correction.
Deliverables
- Read-only reconciliation report and comparison fixture
Rollout and recovery
Expose reports before correction actions; disable report generation when snapshot authority cannot be established.
Value of the work
For the engineer: Practice external contracts, cursor recovery, mapping conflicts, and reconciliation under partial failure.
For the team: Inspect whether integration changes protect inventory correctness and give operators a clear recovery path.
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.