The C4 slice reported this method as dead code: `grep -rn centroidRecallState lib/`
returned nothing but the definition, and the instruction was "wire it into recall
or delete it — do not leave it as furniture".
Neither, and the reason is worth writing down rather than re-deriving:
- It cannot be wired into recall. It calls `centroidStatus`, whose first line is
`countVectored` — a COUNT that C3-k forbids on the per-turn pre-step path. The
scoring path therefore uses `loadCentroid` (one indexed SELECT).
- It should not be deleted. `assertC3RecallUnusable` in test/phase-b-h.test.js
runs the SAME predicate against every C3 mutant, so this method is what pins
Go's `LoadCentroid` semantics (`centroid_store.go:179-185`: a zero-sample centre
is unusable, and the recall side carries no stale bit).
So it is a diagnostic seam, like `StableMem#saveSpaceCentroid`. The name
"Recall-facing projection" was the actual defect — it invites exactly the wiring
C3-k forbids. The name stays (renaming would churn a mutation-shared predicate for
no behavioural gain); the doc now says what it is and what it is not.
Comment only, no behaviour change.
Gates: npm test 300/300, npm run check 12/12.
jianf
16cfdb75d6