Repository navigation
feat(vision-suite): refuse a think-on arm that cannot climb the ladder - #174
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The rung is a result, not plumbing
The
num_ctxa 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 carrynum_ctxat all. "This model needs 32768 to finish a thinking response" is the number that sizes a deployment.Pinning
CTX_MAXto 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.shexits 2 whenCTX_MAXleaves no rung above the think-on start rung.ALLOW_NO_LADDER=1is the deliberate opt-out, and obliges the write-up to say a fixed window was used.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_ctxinto 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=16384to a think-on arm attemperature 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:
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
CTX_MAX=16384 THINK_MODES=onCTX_MAX=32768 THINK_MODES=onCTX_MAXunset,THINK_MODES=onnum_ctx=16384,num_predict=8192CTX_MAX=16384 THINK_MODES=falseALLOW_NO_LADDER=1+ any of the aboveDocs
SPEC: vision harness reusegains H4a and a conformance row, alongside the existing H1–H8.Independent of #168, #171 and #172 — no shared files.
🤖 Generated with Claude Code