The SIGKILL test is a great way to prove it: ten jobs claimed, the worker gone with no cleanup, and a second worker finishing all ten with every step completed exactly once. Keeping decide() pure, so every bug lands either in the decision or in recording it, is the part I would copy first.
We worked on the same promise at Ascendra Ventures for a seed-stage talent platform. Their hiring pipeline did not fail loudly, it just stopped. We rebuilt the profile processor as a durable workflow: urgent profiles run now, the rest are batched, and polling takes over when callbacks go quiet. The goal we wrote down was that every candidate finishes or visibly fails and never gets stuck in the middle. The numbers we shared afterwards were 99.99% system reliability and $0.004 per candidate imported, but the rule was what shaped the design.
How do you plan to handle a job that keeps crashing whichever worker picks it up, so it does not take down each new worker in turn?
Jason Collins