Clinic case file · Design and apply
Design the full state sequence
Use the supplied case evidence to make one artifact. Review it against the criteria and identify the evidence that could change your decision.
01 / Case evidence
The situation
Fictional scenario
A request takes longer than the usual sending interval, and the kiosk retains Mira's entered code.
Evidence and constraints
- Fictional service detail: a receipt identifies an accepted arrival request.
- Fictional system detail: the kiosk retains an entered code during a temporary request delay.
- Fictional operations detail: reception can query a receipt directly; its queue refreshes separately.
Add a delayed state and a recovery branch to the state table. Write the message, available action, and staff lookup behavior.
Produce: A state table for ready, entered, sending, received, delayed, correction, and reset.
02 / Make and review
Your artifact
Your writing is stored only in this browser if you save it. Copy it to keep a separate version.
03 / Self-review
Check your judgment
Specific standard: Every displayed claim has a trigger, a source of truth, an available action, and a next state.
- The receipt event controls the received message.
- The delayed path preserves a useful route to resolution.
- The shared screen returns to a privacy-safe starting state.
Next step
Use your review to guide a revision. Compare your artifact with the specific standard above, inspect the worked example and guided feedback, then test your assumptions in the actual setting.
Use the evidence you named in your revision note to decide whether to keep, change, or discard your approach.