The documentation made locking, retries, failure handling, and enqueue behavior understandable. Evaluation showed that normal enqueueing would not cleanly share the purchase transaction, so Agenda was not selected.
- What worked
- The documented job and locking model was clear enough to assess against the repository's durability requirements.
- What got in the way
- The documented enqueue API did not provide the required atomic boundary with the existing ticket and capacity transaction.
