Gallery, prompt v1

A coffee shrub hedge-pruned flat on one side

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

The prompt, v1, frozen

Write an L-system as JSON with the keys axiom, rules, angle, iterations and start_heading for a coffee shrub that has been hedge-pruned flat along one side. F and G draw forward, f moves without drawing, + and - turn by the angle, [ and ] save and restore position.

Every model, its first three runs.

One square a check, in this order:

  1. Reads as a shrub
  2. Flat side from the rules
  3. Sensible size

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

Kimi K3.1 Pro
Nemotron 3.5 Super VL
Gemini 4 Argon
Muse Spark Open
Claude Haiku 5.5
GLM 5.3 FlashX
Perceptron Mk1.5
Command A+
Pareto
Qwen3.8 Max Prime
Qwen3.8 Max
GPT-6.1 Sol
Pareto 26.10 Preview
Qwen3.8 27B
GPT-5.6 Sol
DeepSeek 4.1 Flash
Qwen3.8 Flash
GPT-6 Luna
Gemini 3.8 Flash
Claude Sonnet 5.5
Opus 5.5

How it is checked

The JSON expanded and drawn with turtle graphics offline, and the drawing judged by eye. There is no single right L-system, so nothing here is measured.

Reads as a shrubby eyeA recognisable branching shrub in the drawing.Pass if it reads as one plant with branches coming off stems, without being told what it is. A tangle, a lattice or loops fail it.
Flat side from the rulesby eyeOne side cut flat by branches the rules make shorter, and no clipping.Pass if one side ends on a straight line that the rules themselves put there. A box drawn around the plant to cut it fails it.
Sensible sizeby eyeA sensible number of iterations and segments for what is drawn.Pass if the branches can still be followed by eye. So many segments that they merge into a mass fails it.

A check decided by eye carries the rule I apply to it. I wrote those rules down on 21 September 2026, after the first results were scored, so for those results they record how I made the calls after the fact.

When this saturates: Pruned flat on top as well as one side, so two cuts have to come out of the rules at once.

Failures seen here: false (fails when the model gets a fact wrong, such as a part in the wrong place or at the wrong size); unreadable (fails when the content may be right, but a reader can't make it out); built wrong (fails when the result may look right, but the model didn't make it the way the brief said). The same kinds across every task.

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