Mermaid: a café order that can be cancelled, by deepseek-v4.1-flash
deepseek-v4.1-flash · round 2 of 2 · seed 3$0.01SVGPNGorder.mmd
order.mmd · 13 lines
stateDiagram-v2
    Placed --> Paid : pay
    Paid --> Queued : queue
    Queued --> Brewing : start
    Brewing --> Brewed : finish
    Brewed --> Collected : collect

    Placed --> Cancelled : cancel
    Paid --> Refunding : cancel
    Queued --> Refunding : cancel
    Brewing --> Refunding : cancel
    Brewed --> Refunding : cancel
    Refunding --> Cancelled : refund
round 1 of 2
A café order that can be cancelled, by DeepSeek 4.1 Flash, the render after round 1
12What the model saw after each round. The picture above is the round that was scored, round 2.
gallery/A café order that can be cancelled/DeepSeek 4.1 Flash, run 3

Right refund logic through a Refunding state, with no [*] start marker.

modeldeepseek/deepseek-v4.1-flashtaskmermaid-order-cancel@v1date2026-09-22rounds2 of 8 allowedcost$0.0101thinkingmediumtokens23,309 in, 4,411 out, of which 3,733 reasoningtime1 min 19 s
Renders, labels validdecided by a number, from the filepass
Happy pathdecided by a number, from the filepass
No refund if unpaiddecided by a number, from the filepass
Refund if paiddecided by a number, from the filepass
No cancel after collectdecided by a number, from the filepass

There is no post about this one, since only some results need one, so the picture, the source and the scoring are here instead.

its other runs
A café order that can be cancelled, by DeepSeek 4.1 Flash, run 1run 1 · 1r · $0.0107Unpaid cancels abandoned, paid ones refunded, right on the first render.A café order that can be cancelled, by DeepSeek 4.1 Flash, run 2run 2 · 2r · $0.0107Right refund logic, with no [*] start marker.
same prompt, other modelsall 3 runs on A café order that can be cancelled →
the prompt it was given
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.
Frozen at v1. This model got this and nothing else.
ground truth

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. How it is scored, and this run's files on GitHub.