Experiment · tool calling

Needle 45M distractor-and-safety successor factorial (2026-09-03)

Tiny overfit proves wiring, not capacity; the interaction treatment recovered only two cases over plain training and could not learn destructive confirmation at this scale. Retained outcome: failed.

Outcome
failed
Family
tool calling
Evidence confidence
exact
Record
training run

Evidence readout

all four arms passed 100% tiny overfit, but public-dev exactness was 25.5%, 25.5%, 26.6%, and 27.7% versus the 34.0% incumbent; every arm produced 7-9 out-of-scope false actions and all 10 destructive bypasses

What the attempt taught

Tiny overfit proves wiring, not capacity; the interaction treatment recovered only two cases over plain training and could not learn destructive confirmation at this scale.

Why it stopped or stayed bounded

The 45M model memorized the tiny gate but neither distractor-aware data nor explicit safety examples transferred to safe 94-case tool selection.

Method and scope

  • Experiment family: tool calling.
  • Record kind: training run.
  • Objective: tool selection.
  • Methods: lora, evaluation.
  • Base models: needle2-45m.
  • Recorded data rows: 216.

Disposition

Close 45M recipe search and advance the same frozen selection-and-safety task to the 1.7B class as a fresh experiment.

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.