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/OrnamentRegister.md

@@ -21,7 +21,10 @@ made once.
 | O1 | hand order | provisional | declared | 2026-08-07 |
 | O2 | who shuffles and deals | provisional | declared | 2026-08-07 |
 | O3 | where a seat is drawn | rule | declared | 2026-08-07 |
-| O4 | card typography and illustration | provisional | declared | 2026-08-07 |
+| O4 | card typography and illustration | rule | declared | 2026-08-07 |
+| O5 | symbols and glyphs | provisional | declared | 2026-08-08 |
+| O6 | colours and design tokens | provisional | declared | 2026-08-08 |
+| O7 | card backs, bill of materials, print manifest | rule | declared | 2026-08-08 |
 
 <!-- ornament-register:end -->
 
@@ -55,12 +58,47 @@ made once.
 
 - **O4 — card typography and illustration.** How a card looks does not
   change what it does. **But it is not ours to invent**: ADR-0015's
-  discipline holds, and `Player_Mats` and `Glossary` — which carry exactly
-  this — are still unvendored (F18).
+  discipline holds.
   **Falsifier:** a card whose meaning is carried by its layout or art
   rather than its text, which is a real possibility in a game about
-  perception and is the reason this is `provisional` rather than `rule`.
-  **Nothing may be declared about these files until they are read.**
+  perception.
+  **Updated 2026-08-08, and the earlier version of this row was wrong.**
+  It said nothing could be declared until `Player_Mats` and `Glossary`
+  were read, and treated both as ornamentation-bearing. They have now been
+  read, and **`Player_Mats.csv` carries GR-R03** — the stress gate — in
+  its `choice_rule` column. Both files are vendored as mechanism; what
+  remains ornamental on a mat is the symbol, the colour and the title,
+  which is why this row is now `rule`-grounded: the rules text lives in
+  columns we read, so what is left is demonstrably decoration.
+
+- **O5 — symbols and glyphs.** `Symbols.csv` gives each concept a glyph,
+  an ASCII fallback and an icon brief. The engine names concepts in words
+  and never in glyphs, so nothing it computes can depend on them.
+  **Falsifier:** a rule that distinguishes two things only by their
+  symbol, or a `symbol_id` that appears in a rules text as the sole
+  referent for something. Note `symbol_id` is currently unread in **six**
+  vendored files, which is what this row licenses — and if that ever
+  becomes load-bearing this row is how we find out.
+
+- **O6 — colours and design tokens.** `Design_Tokens.csv` is a palette
+  with usages. No rule refers to a colour, and seat colour is a label for
+  a seat the engine already identifies by `PlayerId`.
+  **Falsifier:** a rule keyed to colour — *"the red player leads"*, a
+  colour-coded suit — or a component whose identity is only its colour.
+  **Provisional**: nobody has ruled that colour is non-binding; we
+  observed that no vendored rules text mentions one.
+
+- **O7 — card backs, bill of materials, print manifest.** `Back_Designs`,
+  `BOM` and `Print_Manifest` describe a physical print run: stock, cut
+  sizes, quantities to manufacture.
+  **Falsifier:** a *back* that distinguishes two decks the rules treat
+  differently — which is exactly what `back_design_id` would encode, and
+  it is unread in four vendored files. That is a real hazard rather than a
+  theoretical one: hidden information is what card backs are *for*, and a
+  game about concealment could easily make one load-bearing.
+  `rule`-grounded because the engine's hidden information is modelled from
+  the rules text (face-up/face-down, `Hidden` visibility), not from print
+  data.
 
 ## What is deliberately absent
 

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