Skip to content

feat(vision-suite): refuse a think-on arm that cannot climb the ladder - #174

Merged
glennneuber merged 2 commits into
mainfrom
feat/ladder-is-mandatory
Aug 17, 2026
Merged

glennneuber merged 2 commits into
mainfrom
feat/ladder-is-mandatory

Conversation

@glennneuber

Copy link
Copy Markdown

The rung is a result, not plumbing

The num_ctx a think-on cell converges at is a throughput fact about the model. KV size drives decode speed — which is exactly why two cells measured at different rungs aren't comparable on tok/s or req/h, and why the scores carry num_ctx at all. "This model needs 32768 to finish a thinking response" is the number that sizes a deployment.

Pinning CTX_MAX to the think-on start rung doesn't make an arm cheaper. It makes that number unobtainable: escalation is impossible, the cell caps, and the window it actually needed is never discovered.

The guard

run_engine_compare.sh exits 2 when CTX_MAX leaves no rung above the think-on start rung.

  • ALLOW_NO_LADDER=1 is the deliberate opt-out, and obliges the write-up to say a fixed window was used.
  • Think-off is unaffected — it has a fixed cap by design and nothing to climb.
  • A lowered ceiling is still fine. The guard blocks no escalation, not a smaller one.

Why refuse instead of warn

Downstream the failure is invisible. A capped cell and a cell that genuinely converged at the start rung both write a num_ctx into the scores, and every summarizer renders them identically. A warning scrolls past in a run that takes hours; a wrong throughput number gets published.

This is a real defect I committed today

I passed a fixed CTX_MAX=16384 to a think-on arm at temperature 0 — the sampling regime where non-termination is the expected failure — so no capped cell could have escalated.

My stated reason was comparability with the 2026-08-17 low-temperature arm, which has no ladder because it was a hand-written loop (ADR 0028). Its own text says so:

There is no ladder in this arm: it was run directly rather than through run_engine_compare.sh, so every cell sits at a fixed window and a missing score means the model did not finish at that window, not that it failed.

Reproducing a bespoke arm's fixed window inside the sanctioned runner launders its defect into the one place that defect was supposed to be impossible. Comparability against an arm that could not measure the rung is not a reason to also not measure it.

That's the gap this closes: ADR 0028 stops you writing a seventh loop, but nothing stopped you passing the runner a configuration that disables the thing the runner exists for.

Verification

invocation result
CTX_MAX=16384 THINK_MODES=on refuses, exit 2
CTX_MAX=32768 THINK_MODES=on proceeds
CTX_MAX unset, THINK_MODES=on proceeds — num_ctx=16384, num_predict=8192
CTX_MAX=16384 THINK_MODES=false proceeds, unaffected
ALLOW_NO_LADDER=1 + any of the above proceeds

Docs

SPEC: vision harness reuse gains H4a and a conformance row, alongside the existing H1–H8.

Independent of #168, #171 and #172 — no shared files.

🤖 Generated with Claude Code

glennneuber and others added 2 commits August 17, 2026 16:45
The rung a think-on cell converges at IS A RESULT, not plumbing for getting
one. KV size drives decode speed, which is why two cells measured at different
rungs are not comparable on tok/s or req/h, and why the scores carry num_ctx at
all. "This model needs 32768 to finish a thinking response" is the number that
sizes a deployment.

Pinning CTX_MAX to the think-on start rung does not make an arm cheaper. It
makes that number unobtainable: escalation is impossible, the cell caps, and
the window it actually needed is never discovered.

run_engine_compare.sh now exits 2 when CTX_MAX leaves no rung above the
think-on start. ALLOW_NO_LADDER=1 is the deliberate opt-out and obliges the
write-up to say a fixed window was used. Think-off is unaffected — it has a
fixed cap by design and nothing to climb.

REFUSAL RATHER THAN A WARNING IS THE POINT. Downstream the failure is
invisible: a capped cell and a cell that genuinely converged at the start rung
both write a num_ctx into the scores, and every summarizer renders them
identically. A warning scrolls past in a run that takes hours; a wrong
throughput number gets published.

Added after exactly this. A fixed CTX_MAX=16384 was passed to a think-on arm at
temperature 0 — the sampling regime where non-termination is the EXPECTED
failure — so no capped cell could escalate. The stated reason was comparability
with the 2026-08-17 low-temperature arm, which has no ladder because it was a
hand-written loop (ADR 0028). Reproducing a bespoke arm's fixed window inside
the sanctioned runner launders its defect into the one place that defect was
supposed to be impossible. Comparability against an arm that could not measure
the rung is not a reason to also not measure it.

Verified on all four paths:

  CTX_MAX=16384 THINK_MODES=on          -> refuses, exit 2
  CTX_MAX=32768 THINK_MODES=on          -> proceeds (a lowered ceiling is fine;
                                           the guard blocks NO escalation, not
                                           a smaller one)
  CTX_MAX unset THINK_MODES=on          -> proceeds, num_ctx=16384/np=8192
  CTX_MAX=16384 THINK_MODES=false       -> proceeds, unaffected
  ALLOW_NO_LADDER=1 with the above      -> proceeds

SPEC: vision harness reuse gains H4a and a conformance row.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
#176 names two unrelated axes that share one word: the TOKEN ladder
(ladder_sizes / ladder / ladder_tolerance in expectations.toml — image cost
across five fixed geometries) and the CONTEXT ladder (CTX_LADDER — the num_ctx
rungs the runner climbs when a think-on cell exhausts its budget).

H4a and the guard's refusal message both said the bare word while meaning the
second, in a directory where the first is what `ladder` names in the data file.
A reader hitting "cannot climb the ladder" could reasonably have gone looking at
expectations.toml.

Now explicit in the rule, in the guard's comment block and in the operator-
facing refusal text, each pointing at README.md §Terminology. No behaviour
change; the guard's five verified paths are unaffected.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@glennneuber
glennneuber merged commit 200a10a into main Aug 17, 2026
1 check passed
@glennneuber
glennneuber deleted the feat/ladder-is-mandatory branch August 17, 2026 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant