Persona Builder · Adaptive voice bake-off

Which model should drive Charlie?

The Context on demand era includes GPT-6 Luna and Sol reasoning pairs and GPT-6 Astra UltraFast / GPT-6.1 Sol at low reasoning, plus thinking-disabled Wafer 31B FP8, Wafer 26B A4B FP8, Crusoe, and Inworld Gemma 4 baselines, and Muse Spark Open low/medium reasoning on Baseten. All pursue the adaptive docent-full goal through serial real voice CVI. Resource searches and guides load during the conversation. The September 30 WebSocket GPT arms, final-guard-audit Gemma arms, and October 1 A4B arm use the same carrier prompt and RQH #3142 preview; their RQH host is shown below. The earlier four HTTP adaptive-completion arms remain available as the transport baseline. This varies Charlie’s lead model; the shared RQH drafter route stays fixed. Earlier captures use different production carrier versions. The October 16 Inworld row runs the live production carrier 20dc098b (55,222 characters) with a GPT-6 Luna creator; the October 15 Wafer/Muse rows used carrier 4773c607 (54,797 characters) and a Gemini 2.5 Flash creator, so compare them as adjacent captures, not a controlled provider A/B. Historical GLM sequential and Gemma parallel fan-out eras retain 39 arms each. Cross-date and cross-era scores are historical context, not a controlled model or prompt A/B. Provider/configuration failures and unrun arms never receive model scores.

Guided closeout preview: Mercury 3 low and Wafer Gemma 4 FP8 use PR #1913, the real Portal client, the relevant museum PDF, and Gemini 3.6 Flash as creator. Shared test RQH; production carriers are unchanged. One completed capture per model; excluded earlier attempts include a Mercury setup failure, a premature Mercury Test handoff, and a Gemma idle shutdown. Compare the preview arms → Different runtime and creator from historical captures: this is not a controlled prompt-only improvement estimate. Capture findings, aborted attempts, and conversation-quality review →

October 19 Mercury 3: low reasoning directly through Inception, strict tool schemas, production carrier 20dc098b at capture, and GPT-6 Sol as the simulated creator. The older GPT/Muse/Wafer runs used a different carrier and creator. Compare Mercury 3 with Astra, Wafer Gemma 4, and Muse →

The standings rank product outcomes. Final build completeness, timely tool execution, and autonomous handoffs carry the most weight; final build completeness, requirements elicited, reliability, and continuous first-audio latency make up the rest. Deterministic checks remain visible as diagnostic evidence. Adaptive captures that stop before creator completion are not ranked. Click any captured card for its exact shared timeline and transcript.

Tool calls: reviewed first-response execution now caps the Reliability bar and contributes to the overall score. Reliability is the lower of tool-call success and the existing dropped-turn/tool-leakage score. Missing calls count even when no guard intervened. Ambiguous turns are disclosed. Reviewed v4 and legacy scores have separate rankings; legacy reliability has no tool-execution review. Reliability now weighs 25%, autonomy 25%, build 35%, requirements 10%, and latency 5%.

Timing versus eventual success: Tool calls measures first-response dispatch on actionable creator turns, not the validity of emitted calls. Recovery and later batching are shown separately. One draft_pal call can dispatch several shared backend drafters; final completeness is not an independent prompt-quality score. Repeated requests can share the same later repair.

October 15 comparison: Muse Spark Open on Baseten (low and medium reasoning) and Wafer Gemma 4 31B FP8 (thinking disabled) use the same production carrier prompt and production RQH. Compare Muse Spark Open with Wafer Gemma 4 → Each setting has one adaptive capture; the conversations differ.

WebSocket experiment: this opt-in eval adapter reuses provider connections; production CVI transport is unchanged. Provider replay showed a median paired first-output saving of 338 ms for Astra and 361 ms for Sol, with uncertainty for Sol. The voice runs use different adaptive conversations, so their audible latency differences do not isolate transport. Read the measurements, grading corrections, and remaining CVI context race.

Standings click a completed model to inspect its timeline and transcript
Head-to-head pick two to four arms · the page link updates so the comparison is shareable
Scenario matrix

The original at-a-glance diagnostic chart, showing each reasoning arm independently. Its passed/total count is not the standings score: hard thresholds and overlapping checks would otherwise distort the ordering. A timeout or rejected provider credential is harness/configuration evidence; it is not presented as a model-quality failure.

◆all checks clean ◐partial pass ○never called tools ▽dropped a turn ×provider/runtime error, not scored ·not run yet
Draft requirements

Each required field and authored section for the models selected above. Initial means the snapshot at the first draft result; final means the completed capture. Face selection must precede drafting. A dash means the evidence was not captured and is excluded from the check percentage. Presence is mechanical completeness, not a judgement of content quality.

Tool-call matrix

Every tool observed in either the model’s original turn or the turn-guard recovery. Counts are actual calls, not unique field updates.

◆tool called ○never called ×provider/runtime error, not scored
Run behavior one adaptive conversation per reasoning arm
Reasoning is a per-run setting, not a model capability score. Each pair records the effective setting and its separately verified trace evidence. “Lowest” is used where the provider does not support fully disabling reasoning. Blank Charlie turns are counted from the transcript and should be interpreted alongside the config.
Scenario: docent-full. The adaptive creator pursues the same museum-docent requirements across every arm while responding to what each Charlie actually said. The PR #1913 arms preflight the same relevant museum PDF; older captures retain their original source fixtures. Each current run preflights a live readable/presentable PDF and disables the generic per-turn acknowledgement; explicit long-running draft narration remains. Reviewed standings = 25% autonomy + 35% final build completeness + 10% creator requirement coverage + 25% reliability + 5% continuous first-audio latency. Legacy: Standings score = 45% autonomy + 35% build + 10% requirements + 5% reliability + 5% latency. Reviewed v4 reliability is capped by first-response tool-call success; legacy scores are ranked separately. Autonomy itself is 70% self-handoff coverage and 30% guard-free turns. Binary checks are diagnostic gates, not additive weights. Provider/runtime failures are excluded instead of receiving a zero. Timeline and transcript inspectors are rendered by the same core/timing_viz.py component used by the Timeline family.