run 30

docs/pt2-state-map.md

@@ -184,6 +184,39 @@ Current interpretation:
 
 Confidence: medium-high
 
+## Parameterized Selector Behavior
+
+The latest state/value ladder suggests the selector surface is not just
+"command byte picks one response family." It appears parameterized.
+
+Current best read:
+
+- opener command matters
+- opener `state/value` payload matters
+- selector command matters
+- selector `state/value` payload matters
+
+Observed examples:
+
+- `90 + E8`:
+  - `E8 00 80` -> `7A 40 30`
+  - `E8 20 D0` -> `7A 48 3A`
+  - `E8 40 30` -> `7A 50 26`
+  - `E8 60 30` -> `7A 58 26`
+- `90 + E9`:
+  - `E9 00 80` -> `7A 20 D8`
+  - `E9 20 D0` -> `7A 24 FD`
+  - `E9 40 30` -> `7A 28 D3`
+  - `E9 60 30` -> `7A 2C D3`
+- `90 + EC`:
+  - `EC 00 80` -> `FB 40 30`
+  - `EC 20 D0` -> `E4 40 30`
+  - `EC 40 30` -> `FB 50 26`
+  - `EC 60 30` -> `7B 58 26`
+
+That strongly suggests the `state/value` fields are not filler. They likely
+select a page, subtype, class, or data register within the selector space.
+
 ## Downstream Family Branches
 
 ### B1: `E8 -> 7A 50 26`