The FAQ's loss legend claimed a colour code the badges do not use

[pshenok]

577 → 580 tests.

faq_loss_3 said:

Amber means the machine protected itself and kept working; red means the work was dropped.

Two of the nine causes are severity: "dropped" and not red:

maintenance:  { severity: "dropped", color: "#38bdf8" }   // sky
no_capacity:  { severity: "dropped", color: "#a78bfa" }   // violet

NOT ENOUGH RACKS is the most ordinary loss in free play — demand grows in waves past the room's rack count — so the colour a player meets first is the one the legend cannot explain. Having been told colour encodes degraded-versus-dropped, they see violet, which encodes neither, and cannot tell whether the room protected itself or dropped the work.

faq_loss_2 separately enumerated the taxonomy and omitted PLANNED WORK — the only one of the nine missing.

The palette is fine; the sentence was wrong about it

Red means a fault dropped the work. Sky means you scheduled the outage. Violet means nothing failed and the room is simply too small. That is a good code — it just had never been written down. Both locales now say it, and PLANNED WORK joins the taxonomy.

Three rules, written against the palette rather than the sentence

• every cause the sim can record is named in the taxonomy, in both locales;
• the dropped-but-not-red causes are called out by name in the legend;
• the legend does not open with a plain two-colour claim while three colours carry meaning.

So if one of those two causes is ever recoloured red, the test fails and the copy gets simpler — which is the right direction for a legend to move. The mutation that reddens no_capacity demonstrates it.