CB-WP-0037 done: T03 classification and T04 evidence

Reading Player_Mats.csv and Glossary.csv — which O4 had forbidden
declaring about until they were read — found a rule. Player_Mats'
choice_rule column IS GR-R03: at Stress 4-5 choose ATTACK or GROUND unless
you spend a ready Freedom token. The engine's stress_gated and
allowed_under_stress_gate match it exactly, and now have a tripwire.

So Ornamentation.md gains §1.3: the unit is a column, not a file.
Classifying Player_Mats as ornamentation would have thrown a rule away
with the colour swatches. A mixed artifact is normal — a player mat is a
rule printed on a decorated card in the box too. O4 is rewritten and
re-grounded from provisional to rule accordingly.

O5, O6, O7 declared with falsifiers. O7's is not theoretical:
back_design_id is unread in four vendored files, and hidden information is
what card backs are for.

CB-EV-0029 answers T04's question per rule rather than as a count — yes,
every checkable clause — and states the reading that result does NOT
support: it shows GroundRules.md was a faithful secondary source for the
clauses with behaviour to check, not that the engine is correct.

10 of 19 files vendored. Nine still unread, and Rules_Text.csv is the one
that matters: every clause checked here was checked against our own
transcription of it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

specs/Ornamentation.md

@@ -53,13 +53,31 @@ decision, and it is ornamentation. This was the open question in
 CB-WP-0036 and the maintainer settled it: these are ornamental *because
 they are not necessary*, not because nobody chooses.
 
-### 1.3 Why not "ritual"
+### 1.3 The unit is a column, not a file
+
+**Discovered by doing it** (CB-WP-0037 T03). `Player_Mats.csv` looks like
+pure ornamentation — a symbol, a colour, a title for each of six seats —
+and one of its columns is GR-R03 itself:
+
+> *"At Stress 0–3 choose any action. At Stress 4–5 choose ATTACK or GROUND
+> unless you spend a ready Freedom token."*
+
+That is the stress gate the engine enforces in `stress_gated` and
+`allowed_under_stress_gate`. **Classifying the file would have thrown a
+rule away with the colour swatches.**
+
+So a declaration names *what* it ornaments, not *where the bytes live*. A
+mixed artifact is normal: the mat is a rule printed on a decorated card,
+which is exactly what a player mat is in the box too.
+
+### 1.4 Why not "ritual"
 
 `ritual` reads as ceremony only, and half of this category is not
 ceremonial — card stock, a typeface, the drift of a discard, how legible a
 player mat is. **`ornamentation` covers the material and the ceremonial
 together**, and carries the right implication: it is *applied to* the
-thing, and it is not structural.
+thing, and it is not structural — and §1.3 is why *applied to* is the
+right preposition: it sits on something, it is not the something.
 
 Ornamentation is **not decoration in the pejorative sense**. This project
 uses "decoration" for a control that cannot fail (ADR-0006 D3), and that