The execution layer is still being built, so nothing below runs yet. It describes the contract the
errands are being built against, which is fixed.
A task, not a conversation
When an errand starts, you get a task id. The task is the durable thing: it lives on our side, it survives your assistant disconnecting, and it is the same object the Hence app shows you. Close the conversation, come back tomorrow, and the id still resolves to the same errand. That is the reason errands can take days. A rollover waits on a recordkeeper for five to ten business days; a dispute waits on a clock measured in weeks. None of that requires your conversation to stay open.The states
An errand that runs to its own end stops in ready or done, which map onto the READY and DONE
outcome states; an errand the admission gate turns away never starts
and is REFUSED. cancelled is the one terminal state outside that set, because it records your
decision rather than a conclusion the errand reached — see
stopping a task for what it does and does not undo.