I have coached and now judged (just at an invitational) WIDI and I consider code to be something that someone couldn't read in English. So if your instruction said "TL pp 6.8 SRV #3 --> 2.55" I'd call that code. And if you write "12 cm" without defining cm = centimeter, then that's code. But I'm fine with incomplete sentences such as "Blue block on green disk." It lacks a verb and your third grade teacher would mark it off as being a fragment, but it's not code - it's readable. And, the spelling and handwriting needs to be only good enough that it's readable by a very tolerant judge. That's my opinion.
I'd be fine with calling that piece a "Lego chair" or even a "chair" or "chare." If the builder can figure out what the writer is talking about, good enough...
Last week, I giggled at our B team when the writer instructed to "puke the toothpick..." ("No, that's not a puke, it's a poke," she explained)
Unfortunately, the definition of "code" is subjective in this event; some judges, like hscmom, are incredibly
lenient and allow most things to go through. However, some judges, like the technical writing professor who will likely judge your state test, will consider anything poorly qualified to be code and will tier 2 those teams with bad writers.
Like I said, play it safe. If you absolutely need to write things in shorthand, describe the piece/ position precisely, then say in parenthesis what the shorthand version is. You should also do this for unit abbreviations as stated earlier. For example, your first line could read something like this:
Take the white K'nex 8-slot piece with a hole in the center (henceforth white snowflake) and place it on top of the white styrofoam 8 centimeter (cm) by 8 cm block (henceforth base).
Remember, we are proud of every team that participated and you are all winners.