A retry policy copied from a tutorial in 2019

Three attempts, one second apart, applied to every consumer regardless of what it does.

// the inherited default
public int $tries = 3;
public int $backoff = 1;

// what the four consumers actually need:
//   payment capture   long backoff, many attempts —
//                     the gateway recovers in minutes
//   email             a few attempts, then dead-letter
//   search indexing   many attempts, cheap, and a
//                     periodic full rebuild anyway
//   webhook delivery  the published 7-attempt schedule

One retry policy across four consumers means three of them are wrong, and the one that mattered was payment capture giving up after three seconds against a gateway whose outages last minutes. The policy belongs with the consumer because it encodes what failure means for that specific work, which is a domain question rather than an infrastructure default.