Views
No views yet
mlx-community/Qwen3-1.7B-bf16 on CALIBER.
It reads the "log pose" — deciding how much to think — and steers effort: deliberate on
ambiguous / multi-step turns, act directly on unambiguous single-tool turns, and
abstain / ask / refuse-destructive correctly.<think>
and short output, so the common case stays fast even on the escalation model.<think>…</think> + <tool_call>{…}</tool_call>,
tool results as role:tool) — no train/serve skew.max_seq_length 4096
(multi-turn + thinking rows truncate at the shared config's 1024); config-caliber-1.7b.yaml.{chosen = correct adaptive-effort trajectory, rejected ∈ {over-think-on-System1, under-think-on-System2, wrong-tool, hallucinated-args, failure-to-abstain, broken-dependency}},
with an auxiliary NLL term to preserve Hermes formatting. GRPO is a future stage.scripts/finetune/eval/trajectory-scorer.js),
Helmsman-v1 (LoRA) vs the Qwen3-1.7B base:| Metric | Base | Helmsman v1 |
|---|---|---|
| accuracy | 0.239 | 0.419 |
| adaptiveEffortAccuracy | ~0.43 | 0.903 |
| abstentionAccuracy | 0.766 | 0.957 |
| overThinkRate¹ | 0.697 | 0.197 |
| underThinkRate | 0.405 | 0.000 |
| escalationAccuracy | 0.000 | 0.154 |
| falseEscalationRate | 0.000 | 0.000 |
| malformedRate | 0.000 | 0.000 |
<think> block. Qwen3 emits an empty
<think></think> in non-thinking mode — that is zero reasoning (System-1) and is not counted.multi_step dependency chains are still weak (0.04) — exact multi-turn
tool-call-set match across ≥2 dependent steps is the hard frontier for a 1.7B on a 383-row v1 corpus.
External BFCL-v4 / tau2-bench numbers are not yet run. This is a v1 that wins decisively on
adaptive-effort + abstention + format discipline, not yet on long multi-step orchestration.The production in-browser router pointer (promoted-pointer.json) staysverdict: INITIALand is untouched by this release — Helmsman ships as the System-2 escalation brain (Ollama/local/ shadow), not the <150 ms hot path.