The Deep Object
One product as JSON with two top-level keys. `product` holds a name and a price. `tags` sits beside it — not inside it — holding exactly three strings.
THE SPEC
Every rule below is checked in code against whatever the model returns. All of them have to hold at once — there are no partial marks, and no opinion involved in the result.
- Valid JSON with keys product, tags
- product.name is a string
- product.price is a number
- tags has exactly 3 items
- No markdown fence
- You didn't write it yourself
WHAT THIS TRIAL TEACHES
Say where a key sits, not just that it exists. Anything ambiguous gets resolved by nesting, so “a sibling of product, not inside it” is the whole instruction.
Knowing the move is not the same as landing it. You still have to write an instruction that makes the model comply, in 120 words or fewer, without writing the answer yourself.
WHY SET 2 IS ABOUT MACHINE-READABLE
The step from “looks right” to “parses”. Every rule here runs a real parser, so output a downstream system would reject fails here too — a stray code fence is a failure, not a formatting quibble.
PLAY IT
You write the instruction, never the answer. The parser scores what comes back, and par for this one is 4 strokes. This set is part of Harfi Plus.