> Canonical page: https://posttrainllm.com/experiments/pace-next-step-jeff-base-20261005

Experiment · pace planner

# Pace next-step Jeff v1.2 base rejection

Jeff base latency did not preserve clarification, action choice or stopping; qualify each behavior before choosing a fast router. Retained outcome: rejected.

**Outcome**
 rejected

**Family**
 pace planner

**Evidence confidence**
 exact

**Record**
 model evaluation

## Evidence readout

Jeff base: 123 development cases, 33.3% full pass, 6.7% ASK_USER, p50 121 ms; 50 repeat guards.

## What the attempt taught

Jeff base latency did not preserve clarification, action choice or stopping; qualify each behavior before choosing a fast router.

## Why it stopped or stayed bounded

Fast routing did not preserve clarification, action selection, or stopping.

## Method and scope

- Experiment family: pace planner.
- Record kind: model evaluation.
- Objective: tool selection.
- Methods: evaluation, routing.
- Base models: mstrasser/Jeff-Qwen3.5-0.8B@v1.2.

## Disposition

Reject this zero-shot configuration for Pace; no app wiring.

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.

- [evals/pace-next-step-router-20261005/summary.json#results-jeff-base-v1.2-20261005.json ↗](https://github.com/PostTrainLLM/posttrainllm/blob/main/evals/pace-next-step-router-20261005/summary.json#results-jeff-base-v1.2-20261005.json#results-jeff-base-v1.2-20261005.json)
- [https://github.com/HeyPace/pace/issues/200 ↗](https://github.com/HeyPace/pace/issues/200)

[Read the Markdown equivalent →](https://posttrainllm.com/experiments/pace-next-step-jeff-base-20261005.md)

Related evidence

- evidence [Primary proof](https://posttrainllm.com/docs/attempt-ledger/)
- recipe [Applicable recipe](https://posttrainllm.com/recipes/constrained-generation)
- learning path [Learning path](https://posttrainllm.com/learn/paths/evaluation-and-factory)

 Canonical record experiment:pace-next-step-jeff-base-20261005