Worker generation transitions¶

Topics: backends, generation, workers

A HordeWorkerJob coordinates popped work. Each HordeSingleGeneration represents one result and advances through preparation, backend execution, submission, and a terminal outcome. Callers must use the object's transition methods; direct state mutation bypasses invariants and observability.

stateDiagram-v2
    [*] --> waiting
    waiting --> processing: backend starts
    processing --> submitting: result ready
    submitting --> complete: Horde accepts result
    waiting --> faulted: preparation fails
    processing --> faulted: backend fails
    processing --> cancelled: cancellation requested
    submitting --> faulted: submit fails
    complete --> [*]
    faulted --> [*]
    cancelled --> [*]

Progress is meaningful only while backend work is active. A submit response is the confirmation for complete; producing local bytes alone is not completion. Fault and cancellation paths still release backend and dispatch resources.

Code map¶

Worker lifecycle behavior is covered under tests/worker. The state-machine how-to turns this contract into an integration sequence.