Vision: deploy on Qwen3.6-27B (production validation) #13
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Deferred during planning of the initial vision capability (umbrella:
#3). Stage A–C of the vision plan develop against a smaller Qwen-VL
iteration target to keep cycle time tractable; this issue tracks
the deploy-on-target step. Refs:
~/.claude/plans/foamy-twirling-catmull.md.Problem
Iterating directly against Qwen3.6-27B costs full model load time
(minutes) per test cycle and burns a TP setup for each attempt.
Stage A nominates a smaller variant (Stage A0 investigation
identifies which — most likely a Qwen3-VL family member if released,
else Qwen2-VL-2B-Instruct as architecture-adjacent fallback). Once
Stages A–C work end-to-end against the iteration model, this issue
covers what's needed to put the same Rust code in front of the
real 27B in production.
Scope
/archive3/llm-cache/models--Qwen--Qwen3.6-27B/...(or whereverthe production cache lives on beast/benjy/quadbrat).
and the 27B: vision-tower depth, hidden size, patch size,
projector layout. If the iteration model's
vision.rsdoesn'tgeneralise cleanly, factor it.
the TP-vision issue) and benjy and quadbrat.
models.example.tomlto mark Qwen3.6-27B as vision-capableand document the deployment.
Acceptance
with
Qwen/Qwen3.6-27Breturns coherent image-grounded textwith image-token-bearing
prompt_tokens.capabilitiesin their/v1/modelsand seeQwen3.6-27B advertised as vision-capable without any code change.
Blocked by
Stage A–C of the vision plan. The TP-vision issue is the natural
co-traveller for full-quality 27B serving on the existing fleet.
References
~/.claude/plans/foamy-twirling-catmull.md