Skip to content

Commit d1daecb

Browse files
committed
docs: provenance caveat on the §8 fourth mode — bgz-tensor predates turbovec/PolarQuant/helix
Mirrors lance-graph 88dcf6b: the fourth-mode paragraph now notes the adaptive codec was engineered before today's lane inventory existed and points at the queued engineering follow-up review (TD-BGZ-TENSOR-PRE-LANE-REVIEW: i4+i2 cascade vs turbovec Lloyd-Max/NativeLut, Hadamard vs PolarQuant rotation findings, residual coding vs helix — consume-the-lane / demarcate / retire). Knowledge-doc suite green (117/117). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3RyLEbuNSHxxB3NTTrGki
1 parent f0ca32b commit d1daecb

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

.claude/knowledge/pr-x12-h268-morton-wgpu-synergies.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -249,7 +249,12 @@ Hadamard-rotated residual in a three-tier LFD split
249249
`Passthrough` (exact original stored — no index+residual at all), the
250250
next ~20% get an i8 residual, the bottom ~70% the i4+i2 cascade — index
251251
PLACES, residual CORRECTS, and the mold is never forced on rows it
252-
doesn't fit. It is the continuous-field exit
252+
doesn't fit. Provenance caveat: bgz-tensor predates turbovec/PolarQuant
253+
and helix — this records what ships, not current best practice; an
254+
engineering follow-up review is queued (lance-graph
255+
`TD-BGZ-TENSOR-PRE-LANE-REVIEW`: reconcile the i4+i2 cascade vs turbovec
256+
Lloyd-Max/NativeLut, Hadamard vs the PolarQuant rotation findings,
257+
residual coding vs helix — consume-the-lane / demarcate / retire). It is the continuous-field exit
253258
where a bare 256-level index terraces (e.g. elevation); categorical
254259
surfaces (`Signed360` normals, narrow colour) stay flat. Out-of-row like
255260
`Signed360`; the in-row refinement budget remains the turbovec nibble

0 commit comments

Comments
 (0)