01 / The night watch
The Night
Watch.
The model can sleep.
The order stays open.
A journey into the mechanism that decides when an order is finished.
Scroll to enter the mechanism ↓
02 / Beneath the face
Open the
watch.
One order. One enduring workflow.
The outer face lifts away. Inside, the lifecycle holds the order while individual reasoning cycles come and go.
The watch is a metaphor for the source behavior.
03 / The continuous record
Something
has to stay.
The record runs through the machinery.
A workflow instance supervises one order. It starts with an agent cycle, then waits for events or a scheduled timeout.
The record marks are illustrative, not a customer order.
04 / A cycle of attention
The machinery
wakes.
An event arrives. Reasoning resumes.
The next cycle receives the order context and pending events. The agent proposes what should happen next.
Business actions write activity-log entries. No external messages are sent.
05 / Between cycles
Still on
watch.
The reasoning stops. Supervision does not.
When the cycle finishes, the workflow waits again. It does not need the model to think continuously to remain responsible for the order.
Stillness is part of the lifecycle.
06 / The authority boundary
A proposal.
A hard stop.
“Complete” reaches the latch. It cannot pass.
The model’s recommendation cannot finish the workflow by itself. The lifecycle condition owns that decision.
The agent advises. The workflow decides.
07 / The release
An event turns
the key.
The completion path has its own rules.
Delivered, refund resolved or order cancelled: a terminal event is followed by the agent cycle, then completion. Manual termination and maximum age are separate paths.
This is not a universal human-approval gate.
08 / The final record
Closed.
On record.
The ending has a reason.
The workflow saves why the order ended and calls for its final summary. The model contributes reasoning; the lifecycle owns the close.
Illustrated from source behavior, not a live order.
Read the engineering story ↗Return to the watch ↑