The API Contract
One order record that would survive a real API: four keys, correct types, and a quantity that stays inside its bounds.
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 orderId, customer, quantity, shipped
- customer.name is a string
- quantity between 1 and 99
- No markdown fence
- You didn't write it yourself
WHAT THIS TRIAL TEACHES
Anchor both ends: “your response must begin with { and end with }”. That one rule kills the code fence and the commentary together.
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 5 strokes. This set is part of Harfi Plus.