Sequence
The durable reviewer pause
A reviewer step that survives a restart: the pending request is checkpointed and handed back to the reviewer when the workflow is restored.
What it shows
The review step is a typed request and response port in the workflow, not a polling loop. The workflow sends the draft, its citations, the verdict and the versions; the port emits an event to the reviewer UI, which runs as a separate process, and the workflow pauses.
A checkpoint at each superstep persists the workflow's state and its pending requests. If the process restarts or is redeployed in the middle of a review, the state is restored and the open request is emitted again. The reviewer simply sees it again.
The response carries the edited text and the reviewer's identity, and is idempotent by request id: a double click never delivers twice. The framework routes it back to the step that asked, which delivers or refuses, never unreviewed.
This is a reference design for an agentic clinical-trials Q&A assistant. It is a design, not a description of a system built as shown.
Key decisions
- Human review is a port in the graph, so the pause is durable for the same reason the rest of the workflow is.
- Decisions are idempotent by request id.
- Escalation goes to a second port for a safety reviewer: separation of duties is in the graph.
- A pending review has a time limit, and an abandoned one is reassigned, never delivered on its own.