Backend engineering

Model agent tasks so they can be recovered

A task record should preserve enough state to show progress, retry safely, and return finished artifacts after a worker exits.

Start with a clear boundary

Store status, ownership, and timestamps as queryable fields. Keep the user request, generated result, and operational events distinct.

Workers can stop after an external action but before recording success. Idempotency keys and explicit step state reduce duplicate effects.

Decide what users need to retain, what helps debugging, and when each should expire. Recovery does not require keeping every event forever.