step35-cli efc1128fab
All checks were successful
Smoke Test / smoke (pull_request) Successful in 8s
test(M4Max): verify Metal shader bounds checking on M4 Max GPU
Adds automated verification script for issue #125:
- tests/verify_bounds_checking_m4max.sh — validates bounds guards present
                                          and compiles shader on M4 Max
- docs/TESTING_BOUNDS_CHECKING.md — manual verification procedure

Also includes the bounds checking changes from step35/57 branch:
- kernel_fwht_128: data_len parameter + base/d bounds guards
- kernel_turbo4_dequant: src_len, norms_len, dst_len + per-buffer guards
- kernel_attention_turbo4: full buffer length guards (q, k_packed, k_norms, scores)

Closes #125

Co-authored-by: step35-cli <step35-cli@timmy.foundation>
2026-04-26 00:16:25 -04:00
2026-03-30 17:08:45 +00:00
2026-03-30 21:06:49 +00:00

TurboQuant

KV cache compression for local inference on M4 Max MacBook Pro.

What

TurboQuant (Google, ICLR 2026) is a three-stage KV cache compression method:

  1. PolarQuant — WHT rotation + polar coordinates + Lloyd-Max codebook (~4.2x compression)
  2. QJL — 1-bit quantized Johnson-Lindenstrauss residual correction
  3. TurboQuant — PolarQuant + QJL = ~3.5 bits/channel, zero accuracy loss

Why

Unlock 64K-128K context on qwen3.5:27b within 32GB unified memory. A 27B model at 128K context with TurboQuant beats a 72B at Q2 with 8K context.

Status

See issues for current progress.

Roles

  • Strago: Build spec author
  • Cid: Implementation, benchmarks, deployment
  • Locke: Research support, upstream watch
  • John: Quality review
  • Frankie: Coordination

Source Repos

Docs

Description
TurboQuant KV cache compression for local inference — PolarQuant + QJL on M4 Max via llama.cpp/Ollama. Build spec from Strago, build by Cid, coordination by Frankie.
Readme MIT 28 MiB
Languages
Python 90.5%
C++ 6.2%
Metal 2.4%
CMake 0.9%