Fork the sandbox at the decision point

Forty minutes into a task, your agent hits a real decision: rewrite the schema, or patch around it. On a re-provision-from-scratch platform, exploring both means running the first forty minutes twice.

On Hoody, the agent forks. POST /containers/{id}/copy twice: variant-a, variant-b: and both copies carry the full forty minutes of state: files, packages, half-migrated database. Each branch runs its approach in parallel. A judge step compares the results, keeps the winner, deletes the loser.

The exploration that used to be too expensive to do properly: so the agent guessed: becomes the default move. Nothing is re-provisioned. Nothing is replayed.