"A single grade ranks you. A breakdown teaches you. The grader is built to teach."
Three Axes of Seeing
Once Procrustes has aligned away the global pose, three things about your construction can still be wrong — and they are genuinely independent skills, so the grader scores each one separately. Angle: are the tilts and orientations between parts correct — the set of the jaw against the brow, the turn of the box? Proportion: are the relative sizes right — cranium to face, upper arm to forearm? Placement: are the internal parts positioned correctly relative to each other — do the eyes land on the right third, does the far edge sit where it should? Three faculties, measured on their own axes.
Why Not One Number
Collapse those three into a single grade and you've thrown away everything useful. '72%' tells you that you were off; it does not tell you where, and 'where' is the only part you can act on. Two students can score an identical 72 while being wrong in completely different ways — one nails proportion but skews every angle, the other has perfect angles and mangled proportions — and they need opposite practice. A single number hides that difference; the sub-scores expose it. The breakdown is what turns a grade from a verdict into a diagnosis.
The Composite Is Advisory
The grader does compute a composite score, but it labels it advisory on purpose. It's a rough roll-up for a glance — a way to sense the overall attempt at a distance — explicitly not the real signal. That labeling is a design decision with teeth: it steers you away from optimizing the one number (which teaches nothing) and toward the sub-scores (where the learning is). An advisory composite says, in effect, 'here's the summary if you want it, but the three numbers under it are the ones that will make you better.'
Feedback That Says Where
Underneath the drawing-specific detail is a universal truth about feedback: good feedback localizes. 'Wrong' is weak. 'Wrong here, in this specific way' is strong, because it points at the next action. It's the same reason a per-landmark reprojection error beats one global number, the same reason a stack trace beats 'it crashed,' the same reason a code review that names lines beats a thumbs-down. The three sub-scores are Loomis localizing the error for you — refusing to let the grade be a mood, insisting it be a map.