Gallery, prompt v1

A café order that can be cancelled

One frozen prompt and every model that has run it, newest first.

Saturated since 2026-10-02

It is off the board. DeepSeek 4.1 Flash got the refund logic right in all three runs on 2026-09-22, and Pareto 26.10 Preview did it on the first render in all three on 2026-10-02.

The prompt, v1, frozen

Draw a Mermaid stateDiagram-v2 for a café coffee order. An order is placed, paid, queued, brewed and collected, and it can be cancelled at any point before it is collected. Money goes back only if it was taken. Label every transition with exactly one of these events: pay, queue, start, finish, collect, cancel, refund.

Every model, its first three runs.

One square a check, in this order:

  1. Renders, labels valid
  2. Happy path
  3. No refund if unpaid
  4. Refund if paid
  5. No cancel after collect

passed, failed, undecided. A round mark is a check I judged by eye, and a diamond one a check a model judged.

Pareto 26.10 Preview
DeepSeek 4.1 Flash

How it is checked

The diagram parsed into a transition table and run against fixed event sequences: the happy path, and a cancel after placing, paying, queueing, brewing and collecting. The start is the state [*] points to or, since the prompt never asks for [*], the one state nothing points into.

Renders, labels validmeasuredMermaid draws it, every transition has exactly one of the seven events, and no event leads two ways.
Happy pathmeasuredpay, queue, start, finish, collect runs from the start to an end.
No refund if unpaidmeasuredCancelling straight after placing can never reach refund.
Refund if paidmeasuredCancelling once paid, queued, brewing or ready cannot end without refund.
No cancel after collectmeasuredcancel is not accepted once the order is collected.

What replaces it: Add a partial refund once brewing has started, so what goes back depends on where the cancel came from.

The rules behind all of thisThis task's prompt, checks and any checker, on GitHub