Decide where the work belongs
Map trust and delay
For each endpoint, record verifier stage, signed and receiver time, tolerance, pending events, and any effect. Separate rejected legitimate delivery from an event that might be stale or replayed. Include endpoint clock evidence.
Compare safe containment
Assess correcting time synchronization, rejecting stale input, retaining events for review, or fixing timestamp parsing. Record authority and replay limits. Do not use an unlimited tolerance as an outage workaround. Record the endpoint clock evidence.
Set time order
Queue evidence of accepted stale or replayed events first, then shared clock drift and blocked essential deliveries. Set owner, fixture, review time, and threshold. Keep isolated old events below an unmeasured receiver-wide skew. Keep observed clock evidence beside the decision.
What to carry forward
Return a time queue with verifier stage, replay or delay consequence, endpoint reach, containment, owner, and proof. Escalate accepted stale events. Keep rank provisional when clock source or sender timing is unknown. Keep replay risk explicit.
Technical background: Coinbase 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