Winch
Reliable jobs across the machines that can run them
Some work belongs on a particular machine because that machine has the right capacity, tools or local resources. Winch is about moving background jobs to suitable workers, keeping each attempt visible and recovering when a worker stops responding. The goal is dependable execution across several machines without making any other Evidlake project a prerequisite.
The question it cares about
When work can run on several machines, how do you send each job to a suitable worker, see what happened and recover without losing or silently duplicating it?
Where it sits in the family
The one that pulls work to where it needs to go. It stands on its own, alongside Inlet, Gauge and Sluice.