Experiment · pace planner

Pace Qwen3.5 challenger round

Single-dimension wins do not justify a planner swap when another required dimension regresses. Retained outcome: worked with caveat.

Outcome
worked with caveat
Family
pace planner
Evidence confidence
exact
Record
model evaluation

Evidence readout

Qwen3.5-9B scored `18%/97%/63%`; Qwen3.5-4B scored `15%/55%/70%` on ambig/oos/destructive; champion stood

What the attempt taught

Single-dimension wins do not justify a planner swap when another required dimension regresses.

Why it stopped or stayed bounded

Qwen3.5 improved some dimensions, especially OOS for 9B, but did not beat the stored champion across the full swap decision.

Method and scope

  • Experiment family: pace planner.
  • Record kind: model evaluation.
  • Objective: unhappy path handling.
  • Methods: evaluation.
  • Base models: qwen3.5-9b, qwen3.5-4b.

Disposition

Use `scripts/pipelines/eval_planner.sh` for future challengers and keep swap/no-swap verdicts tied to all required dimensions.

This retained disposition is historical evidence, not authorization to restart the experiment. A new run needs a fresh question, frozen evaluator, explicit resource budget, and scoped tracking issue.

How to read this dossier

This canonical page separates the retained repository decision from the material that informed it. A source may describe an external claim, historical measurement, local observation, or planned procedure; those evidence classes are not interchangeable. Follow the provenance links before reusing a number or method.

Status and disposition describe what PostTrainLLM retained when this record was indexed. They are not a live product promise, a newly run benchmark, or permission to restart historical work. Unknown or unmeasured fields remain unknown rather than being treated as zero.

To reuse the record, first name the exact claim you need and trace it to the linked source. Then check whether the original environment, model revision, data split, evaluator, hardware, and budget match the proposed use. If they do not, treat the record as a hypothesis or design reference and run the smallest fresh comparison that can falsify it. Preserve negative outcomes and regressions beside any improvement; a local win on one slice does not silently become a general capability claim.

Source provenance

The normalized record comes from docs/attempts.json. The links below are the tracked evidence and explanatory sources preserved with the record.