A design of your own

Somewhere to draw whatever you are actually working on. Write down what it has to do — in your own words, no format — and it appears beside the canvas exactly as you typed it. Add requirements if you have them and they become the checklist you tick off, exactly as on a task from the pool; leave them empty and the reviewer reads the description instead, saying where it does not settle something rather than marking you against a rule you never wrote.

Name

What it has to do

0/4000 characters. Vague in, vague out: with no numbers and no stated failure tolerance, a review can only say so much — and it will tell you that rather than invent a standard to mark you against.

Requirements, one per line — optional

Each line becomes one checkbox beside the canvas, and what you tick goes to the reviewer along with the diagram — the gap between the two is the sharpest thing a review can point at. One outcome per line, with a number wherever you have one: “answers in under 300 ms at peak” can be argued about, “must be fast” cannot.

Constraints, one per line — optional

What the design has to live with rather than achieve: what you may not change, what you may not add. They are not ticked off — they are shown beside the canvas and the reviewer is held to them, so a design is not marked down for missing something a constraint forbids.