KB-63BF

FIX3 08 — Scale Blocking

2 min read Revision 1

SUPERTRACK H. Goal: do not solve keyset/resume here, but ensure scale absence is a HARD blocker until 2.6B and beyond.

qt001_capability_contract enumerates the required scale capabilities — keyset_pagination, resume_watermark, automatic_refresh, representative_perf_gate — each satisfied=false by default. A table-level CHECK enforces that a capability may be marked satisfied only with a proof_object and a non-NONE proof_kind (OBJECT / BEHAVIORAL / PERF_GATE), so no capability can be flipped green by metadata alone.

v_qt001_scale_blocking_guard_v3: capabilities_total 4, capabilities_satisfied 0, capabilities_unsatisfied 4, scale_not_safe true, scale_safe false, unsatisfied_keys keyset_pagination,resume_watermark,automatic_refresh,representative_perf_gate. Because scale_safe is false, the readiness v6 APPLY gate scale_capability_satisfied is RED, contributing to BLOCKED. The no-bypass proof includes scale_not_safe as a blocked precondition. Scale will remain blocking until Stage 2.6B implements real keyset/resume/refresh/perf objects and records their proof in qt001_capability_contract; the existing full-rescan fn_qt001_plan_all remains SCALE_NOT_SAFE.

Back to Knowledge Hub knowledge/dev/reports/architecture/birth-stage2-6a-fix3-qt001-exact-control-contract-authority-lockdown-2026-06-06/08-scale-blocking.md