Resume an interrupted agent without repeating side effects
one move: separate intent from effects
Open the code pane immediately, then use the Spec tab, optional design question, tests, and artifact when you want them.
Finish each move before carrying the artifact forward.
Long-running agents need checkpoints, retries, and idempotency keys so a crash does not duplicate an email, payment, or deploy.
Deliverable: State the system invariant in one sentence.Apply events to a workflow state with a completed-key set; duplicate effects become no-ops and failed steps can resume.
Deliverable: Type the deterministic core.Replaying the same event twice yields the same state, unknown transitions are rejected, and checkpoints are serializable.
Deliverable: Record a normal case and a boundary case.Crash after the effect but before the checkpoint, retry a tool, and deliver events out of order.
Deliverable: Name the failure signal and its guard.A durable workflow snapshot, idempotency ledger, and recovery transcript.
Deliverable: Save the contract, evidence, and handoff note.Replaying the same event twice yields the same state, unknown transitions are rejected, and checkpoints are serializable.
Crash after the effect but before the checkpoint, retry a tool, and deliver events out of order.
A durable workflow snapshot, idempotency ledger, and recovery transcript.
Deriva-authored extension beyond the supplied PDF. The five moves are Deriva’s implementation contract for this project.