Keep the lesson for the next incident
Write the reservation contract
State when availability is advisory, when a reservation becomes authoritative, how quantity is decremented, and what payment or cancellation does to the reservation. Include version or timestamp expectations and the truthful shopper state while a conflict is unresolved.
Keep concurrency fixtures
Save synthetic traces for competing one-unit attempts, quantity edits, delayed reservation, payment failure, and refresh. Assert inventory and order outcomes together. Keep the fixtures small enough to run whenever cart, payment, or fulfillment code changes.
Define recurrence triggers
Reopen review when a paid order lacks its reservation, a failed attempt leaves stock held, or a shopper sees availability after the last unit is claimed. State catalog scope, sampling limits, and the owner for new contention cases.
What to carry forward
Close learning with the reservation contract, race fixtures, fallback wording, and recurrence triggers tied to durable records. Keep catalog and concurrency coverage limits explicit so a passing single-cart test is not mistaken for broad proof.
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