docs(v4.0.0): the opcode's accounts are left unwired for now

Captain Bob, 2026-10-05: observe the opcode counts, build no opcode patron
layer yet; likely needed at the FPGA; keep it available.  Amends section
2.7: word patrons do not become opcode patrons now.

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

docs/v4.0.0/V3-PARITY.md

@@ -370,6 +370,31 @@ So these earlier statements are withdrawn:
 
 What is actually open is what the opcode's own rules are.
 
+## 1h. The opcode's accounts: left unwired for now (2026-10-05)
+
+Asked what the opcode's own accounting rules are, Captain Bob: "For the
+moment, I think we're going to leave it unwired and kind of maybe just
+make some observations on it and see if we even need it, as far as
+opcodes are concerned. I think we will when we go to FPGA, but for now,
+let's just hang on to the thought and make sure that it's available if
+needed."
+
+So:
+
+- No opcode patron layer is built. Opcodes are not wired to the Stadium.
+- The node goes on counting each opcode as it retires
+  (`v4_heat.op[32]`, `v4/src/heat.c`), and the anti-clock. Those counts
+  are real and are there to be observed. Nothing reads them to decide
+  anything.
+- This amends section 2.7 and the reading in section 1c: a VM's word
+  patrons do **not** become opcode patrons now.
+
+**Reading, stated to Captain Bob and to be corrected if wrong:** with
+opcodes unwired and v4 = v3 functionally, a word on v4 keeps a word's
+accounts as v3 has them — its Stadium cell by `stadium_words.c`'s rules,
+and the `execution_heat` the ACL reads — taken at the call hook of
+section 1f, which is where a v4 node dispatches a word.
+
 ## 2. Row 3: physics and per-word heat
 
 ### 2.1 What v3 does