Decide where the work belongs
Map ambiguity and effect
For each event, record delivery ID, resource, operation, parser result, prior state, and effect. Separate safe review from a possible repeated mutation. Keep two similar events distinct in the evidence.
Compare identity remedies
Assess fixing field extraction, using a documented header, retaining an unknown state, requesting contract clarification, or pausing effects. Record authority and recovery. Do not invent a deduplication key from mutable payload order.
Set identity order
Queue effect-bearing shared handlers and existing duplicate risk first, then isolated missing fields and observability work. Set owner, fixtures, review time, and evidence threshold. Keep resource-only routing below a proven stable event ID.
What to carry forward
Return an identity queue with available key, ambiguity, effect risk, safe containment, owner, and proof needed to reprioritize. Escalate unknown or irreversible work. Keep ranking provisional when the sender schema is incomplete. Include two distinct events for the same resource in the ranking evidence; treating their shared resource key as identity can discard legitimate work.
Technical background: Shopify developer documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow