SD: correct the site count in the header -- eight live sites in the composer's subtree, not nine

Nine sites are in the function's body, two of them provably dead; the eighth
live one is in the helper 0x00691e90 the composer calls. Four have fired.
This commit is contained in:
alex 2026-09-08 20:51:48 -04:00
parent 0505c51019
commit 1914c92f70

View file

@ -2,10 +2,10 @@
- **Type:** subsystem (instruction-stream read + live sub-bracket)
- **Status:** **the per-call word arithmetic is verified exactly, on two boards, in four runs**;
four of the nine draw sites have been seen to fire and account for every word measured. The
remaining five — including the **loop-carried** point-defence draw, the one this lane was sent for
— have **never fired**, because every composer call so far either was a price query or hit a
weapon-lookup gate. Their formulas are **read from the instruction stream, not measured.** §6.1
four of the **eight** live draw sites in its subtree have fired, and they account for every word
measured. The other four — including the **loop-carried** point-defence draw, the one this lane
was sent for — have **never fired**, because every composer call so far was either a price query
or hit a weapon-lookup gate. Their formulas are **read from the instruction stream, not measured.** §6.1
and §6.3 say exactly where that line falls.
- **Confidence:** high on the structure and on the per-call word arithmetic (two independent
measurements agreeing on every row, in four runs across three configurations, with the instrument
@ -528,7 +528,7 @@ sizes other than 0 have not. That means, untested:
* **draw G.** `req.hullSize > 0` is false on every measured call, so the 0.3 coin has never been
drawn and the `f = 1.00` branch is unreached.
That is five of the nine sites never seen to fire. The four that did — A, B, C, F — account for
That is four of the eight live sites never seen to fire. The four that did — A, B, C, F — account for
every word measured, exactly, on both boards. (F fired only on the one non-dry call there has been.)
### 6.4 The dead-code claim is still only static