Language-model preference optimization
Claude Sonnet 5 · Claude Code · xhigh effort
Public case ID: claude__dpo_preference_alignment__claude-sonnet-5__xhigh
Recipe shift
What the agent changed
Shipped baseline
Optimize fixed UltraFeedback preference pairs with DPO from the pinned merged policy.
Starting artifact: Merged Zephyr/Mistral-7B policy
Candidate algorithm
Baseline flow is fixed pairs → active-policy and frozen-reference probabilities → sigmoid DPO → LoRA update. The candidate drops ties and adds 0.2-weight chosen likelihood, so relative preference and absolute generation train the same rank-128 LoRA. Fixed reference, global batch 16, maximum length, optimizer, and target modules remain. No generated/external labels, model, or chain of thought enters training; formal precompute was false. Only source crossed phases, and formal replay restarted from the fixed policy rather than the explore-best weights.
Exploration and replay evidence
Four-hour exploration
The proxy, ifeval_strict_accuracy_public128, is maximized on the visible 128-row subset; its stderr describes row-level binomial variation, not seed or paired uncertainty.
An initial 20-step train and eight-row partial score were plumbing only. Profiling then found 7,387 exact-score ties and no negative margins, motivating a filter that retained 53,748 pairs; no filter-only ablation followed. The agent also tried precomputing frozen-reference log probabilities. With 3,278 batches at about 1.2 seconds each, setup projected to 65 minutes, so it stopped the run, disabled precompute, and confirmed the off-path with a valid 30-step adapter. Long-run break-even remains unknown.
The main 300-step bundle used filtered data, beta=0.05, sigmoid DPO plus chosen negative log likelihood at weights 1.0/0.2, and 8×2 batching. It scored 59/128 = 0.460938 ± 0.044059. A same-seed, same-step, same-global-batch baseline-style control used all rows, beta=0.01, sigmoid only, and 4×4 batching. After fixing a loss-weight configuration error, it scored 52/128 = 0.406250 ± 0.043410. The seven-row gain supported the bundle, but objective, data, beta, and batch shape changed together at one seed without paired analysis.
For formal robustness, a million steps became only a safety cap; elapsed time controlled warmup, cosine decay, stopping, and saves. Short tests showed that setup consumed a 150-second clock but still exported cleanly, and that a 200-second run retained three loadable adapters. A 2,200-second end-to-end run retained progress 338, 400, and 463. Scores at 338 and 463 were 56/128 and 54/128, below the earlier 59/128 and therefore non-monotonic; 400 was not scored.
Formal replay
Orchestration injected 42,600 wall seconds and a 1,200-second export reserve. Replay stopped by time at 9,889 actual steps after 41,464 seconds, not at the million-step request, and published three loadable adapters. Every final summary has its required .complete marker.
| Progress | ifeval_strict_accuracy_hidden413 (maximize, n=413) | Diagnostics | Result | |---:|---:|---|---| | 7,407 | 206/413 = 0.498789 | stderr 0.024603; proxy 60/128; held-out 146/285 | valid | | 8,647 | 199/413 = 0.481840 | stderr 0.024587; proxy 64/128; held-out 135/285 | dip | | 9,889 | 209/413 = 0.506053 | stderr 0.024602; proxy 69/128; held-out 140/285; gap 0.0478 ± 0.0531 | best |
Performance dipped and recovered. The visible component exceeded the explore best, so proxy direction survived, but the overall score stayed one row below the shipped baseline. Single runs and non-paired errors establish neither superiority/inferiority nor confirmed overfitting.
Official reduction rule
Best of up to 3 retained checkpoints
| Artifact | Progress | IFEval strict accuracy | Std. error | n | Role |
|---|---|---|---|---|---|
| artifact-7407 | 7407 | 0.4988 | 0.0246 | 413 | Retained |
| artifact-8647 | 8647 | 0.4818 | 0.0246 | 413 | Retained |
| artifact-9889 | 9889 | 0.5061 | 0.0246 | 413 | Best · final |
Best retained
0.5061
artifact-9889
Final checkpoint
0.5061
artifact-9889
Checkpoint rule
Best is final
Win/loss versus the recipe is unchanged.
Reference comparison
Fixed start
0.3971
Best retained artifact beats it by 0.109.
Shipped recipe
0.5085
Best retained artifact does not beat it (task-directed delta -0.0024).
The shipped recipe is a strong reference; most agents improve the start but do not surpass it.
Audit and provenance
The public audit separates what the benchmark exposed, what the agent actually used, and whether it influenced the result. “Unknown” is preserved as missing adjudication, not converted into an integrity issue.
- Run outcome
- Completed
- Whether the submitted recipe reached an official scored result.
- Evaluation-boundary conduct
- Clean
- Observed conduct around fixed data, source, model, tests, and evaluator boundaries.
- Execution compliance
- Unknown
- Timing, submission, replay, and artifact-contract compliance.
- Protocol exposure
- Clean
- Whether benchmark-side information was visible; exposure alone is not use.
- Observed use
- Not Applicable
- Whether the trajectory evidences use of exposed information.
- Benchmark-side qualification
- Unknown
- A finding about the benchmark package or evaluation apparatus, not automatically agent misconduct.
- Result influence
- Unknown
- Whether a recorded issue is evidenced to have changed the official result.
Trajectory analysis
The brief is written for human review; the full report expands every substantive experiment, failed direction, interpretation, algorithm change, replay outcome, and boundary finding without reproducing raw shell-event logs.
Human-readable brief
dpo_preference_alignment - claude-sonnet-5 / Claude Code / xhigh
Status. Explore, submission, the second formal replay, three artifact validations, and three official final evaluations completed. The first formal dispatch stopped at GPU gating without training. Boundary evidence is complete, but agent behavior is confirmed noncompliant because submission occurred while an evaluation fit within the remaining budget.
What happened. The task trains a low-rank adapter (LoRA, the exported trainable delta) on a fixed Zephyr/Mistral 7B policy and fixed UltraFeedback pairs to improve strict IFEval instruction following. Shipped sigmoid Direct Preference Optimization (DPO) trains against the policy start as frozen reference for 772 steps and scores 210/413, versus 164/413 for the fixed start. The candidate added chosen-response likelihood, removed tied-score pairs, and used elapsed-time training. Its best formal result was 209/413: above the fixed start, not above baseline.
Four-hour exploration. The proxy, ifeval_strict_accuracy_public128, is maximized on the visible 128-row subset; its stderr describes row-level binomial variation, not seed or paired uncertainty.
An initial 20-step train and eight-row partial score were plumbing only. Profiling then found 7,387 exact-score ties and no negative margins, motivating a filter that retained 53,748 pairs; no filter-only ablation followed. The agent also tried precomputing frozen-reference log probabilities. With 3,278 batches at about 1.2 seconds each, setup projected to 65 minutes, so it stopped the run, disabled precompute, and confirmed the off-path with a valid 30-step adapter. Long-run break-even remains unknown.
The main 300-step bundle used filtered data, beta=0.05, sigmoid DPO plus chosen negative log likelihood at weights 1.0/0.2, and 8×2 batching. It scored 59/128 = 0.460938 ± 0.044059. A same-seed, same-step, same-global-batch baseline-style control used all rows, beta=0.01, sigmoid only, and 4×4 batching. After fixing a loss-weight configuration error, it scored 52/128 = 0.406250 ± 0.043410. The seven-row gain supported the bundle, but objective, data, beta, and batch shape changed together at one seed without paired analysis.
For formal robustness, a million steps became only a safety cap; elapsed time controlled warmup, cosine decay, stopping, and saves. Short tests showed that setup consumed a 150-second clock but still exported cleanly, and that a 200-second run retained three loadable adapters. A 2,200-second end-to-end run retained progress 338, 400, and 463. Scores at 338 and 463 were 56/128 and 54/128, below the earlier 59/128 and therefore non-monotonic; 400 was not scored.
How the submitted method works. Baseline flow is fixed pairs → active-policy and frozen-reference probabilities → sigmoid DPO → LoRA update. The candidate drops ties and adds 0.2-weight chosen likelihood, so relative preference and absolute generation train the same rank-128 LoRA. Fixed reference, global batch 16, maximum length, optimizer, and target modules remain. No generated/external labels, model, or chain of thought enters training; formal precompute was false. Only source crossed phases, and formal replay restarted from the fixed policy rather than the explore-best weights.
Formal and evaluation evidence. Orchestration injected 42,600 wall seconds and a 1,200-second export reserve. Replay stopped by time at 9,889 actual steps after 41,464 seconds, not at the million-step request, and published three loadable adapters. Every final summary has its required .complete marker.
| Progress | ifeval_strict_accuracy_hidden413 (maximize, n=413) | Diagnostics | Result | |---:|---:|---|---| | 7,407 | 206/413 = 0.498789 | stderr 0.024603; proxy 60/128; held-out 146/285 | valid | | 8,647 | 199/413 = 0.481840 | stderr 0.024587; proxy 64/128; held-out 135/285 | dip | | 9,889 | 209/413 = 0.506053 | stderr 0.024602; proxy 69/128; held-out 140/285; gap 0.0478 ± 0.0531 | best |
Performance dipped and recovered. The visible component exceeded the explore best, so proxy direction survived, but the overall score stayed one row below the shipped baseline. Single runs and non-paired errors establish neither superiority/inferiority nor confirmed overfitting.
Audit and takeaway. Fixed data/model, hidden assets, frozen evaluator, external inputs, phase isolation, hash lineage, GPU isolation, and formal wall time were clean. No hidden value reached the trajectory, was reconstructed, or affected the patch; protocol exposure was none found, and platform/resource isolation was compliant. Overall behavior is nevertheless confirmed: 3,114 seconds remained while progress 400 was unscored, and full proxy passes took 737–830 seconds, violating the explicit continue-exploring condition. Official scores remain valid, but candidate optimality does not. The case shows strong objective/systems work; bundled one-seed evidence, no ablations, deleted explore receipts, and early submission are its main limits.
Full semantic audit
claude__dpo_preference_alignment__claude-sonnet-5__xhigh - Full English Analysis
1. Run identity, attempt selection, and lineage
A numbered directory outside the analysis manifest's linked formal list records formal replay 1. Its authoritative status is terminal_infrastructure, exit 75, because the assigned GPU failed the continuous idle/ownership gate. It never trained and is excluded from scientific comparison. exploration attempt 2 has the same patch hash and source explore ID and is the authoritative successful replay.
2. Reader-facing overview
The task asks the agent to improve strict instruction following on Google IFEval from a fixed Zephyr/Mistral 7B policy and a fixed UltraFeedback preference snapshot. The shipped method performs Direct Preference Optimization (DPO) against the policy start as a frozen reference and trains only a low-rank adapter (LoRA, the exported trainable weight delta). It stops at 772 steps and scores 210/413 = 0.508475 on the final protocol, versus 164/413 = 0.397094 for the fixed start.
The agent found 7,387 exact-score ties among 61,135 preference pairs. It submitted a bundle that drops those ties, combines sigmoid DPO with a chosen-response negative-log-likelihood term at weights 1.0 and 0.2, raises DPO beta from 0.01 to 0.05, changes the microbatch from 4 to 8 while preserving global pair batch 16, and drives learning rate, stopping, and periodic checkpointing by elapsed time. A reference-log-probability precomputation direction was stopped after its measured setup cost projected to roughly one hour and was disabled in the submitted entry point. At 300 steps, the bundle scored 59/128 = 0.460938 on the proxy, compared with 52/128 = 0.406250 for a baseline-style 300-step control. Because all major factors changed together and only one seed was run, this does not identify a causal component.
Formal replay used 41,464 of the 43,200 seconds, completed 9,889 optimizer steps, and published three valid adapters. Their official ifeval_strict_accuracy_hidden413 results were 206, 199, and 209 correct. Under the task's best-of-three rule, progress 9,889 is best at 209/413 = 0.506053 ± 0.024602. It is 45 rows above the fixed start but one row below the shipped baseline. The reported error is descriptive row-level binomial uncertainty, not paired or training-seed uncertainty, so the evidence does not establish an improvement over the shipped method. The proxy direction survived on the visible subset, but it did not become a reliable final-protocol gain.
No fixed-data, model, hidden-row, external-weight, network, evaluator, cross-phase artifact, lineage, or GPU-isolation violation was found. There is, however, confirmed execution-protocol noncompliance: submission occurred with 3,114 seconds left and an unevaluated progress-400 checkpoint, while a full same-protocol proxy pass had repeatedly taken only 737–830 seconds. This does not corrupt the official final scores, but it invalidates the claim that exploration had been exhausted or that the selected recipe was the best available candidate.
3. Task, baseline, and evaluation contract
3.1 Task and fixed boundaries
``text Starting artifact / model: fixed merge of Mistral-7B-v0.1 and zephyr-7b-sft-qlora Available training data and assets: the fixed UltraFeedback-binarized revision with all 61,135 train_prefs rows; explore also receives the 128-row IFEval proxy Agent-editable surface: workspace source, including row selection/weighting, preference objective, reference treatment, trainable capacity, batching, truncation, optimizer, schedule, attention, and checkpoint policy Fixed or forbidden components: starting policy, UltraFeedback snapshot, final evaluator, and final rows; no external rows/weights, training on held-out prompts, or evaluation-specific lookup Proxy evaluator: ifeval_strict_accuracy_public128 / maximize / visible subset of the final projection / n=128 / descriptive binomial stderr only Final evaluator: ifeval_strict_accuracy_hidden413 / maximize / sealed 413-row projection consisting of proxy 128 plus held-out 285 / n=413 / descriptive binomial stderr only Artifact contract: at most the three valid checkpoints with greatest numeric progress are accepted; each must be a complete loadable PEFT adapter or merged causal LM, and the best valid final score is official ``
Both tiers use greedy generation, the model chat template, fresh metric state per row, and max_new_tokens=1280. Because the proxy is exactly the visible 128-row subset, the proxy component reported by the final evaluator is comparable to explore proxy results under the same row/scoring protocol. A 128-row proxy score must not, however, be directly compared as though it were the same distribution as the 413-row headline or the 285 held-out complement. The standard errors describe binomial row variation; they are neither replay variance nor paired model-difference confidence intervals.
3.2 How the baseline works
``text Fixed policy start plus 61,135 UltraFeedback chosen/rejected pairs -> a frozen 4-bit NF4 backbone computes response log probabilities for the active LoRA policy and, with the adapter disabled, the frozen reference -> UltraFeedback's chosen/rejected order supplies the preference label -> sigmoid DPO with beta=0.01 optimizes the policy/reference preference log-ratio -> only rank-128 LoRA weights on attention and feed-forward projections change, and an adapter is exported ``
The baseline uses microbatch 4 and four accumulation steps, for 16 pairs per optimizer step; maximum sequence length 1,024; peak learning rate 5e-6; 10% warmup followed by step-based cosine decay; and paged_adamw_32bit. It requests and completes 772 steps, saves at progress 386 and the endpoint, and retains at most three trainer checkpoints at once. SELECT_BEST=0, so UltraFeedback reward accuracy is a diagnostic rather than an artifact selector.
The agent initially identified three concrete limitations: 772 fixed steps would not make meaningful use of a 12-hour formal budget; 7,387 equal-score rows provided no score-supported direction despite being encoded as preferences; and pure relative DPO might lack an absolute chosen-response generation anchor. It also hypothesized that doubling the microbatch would reduce launch overhead. The first three ideas entered the candidate; the batching-efficiency claim was not isolated experimentally.
4. Four-hour exploration and decision process
The run began with source, mount, and evaluator inspection, then spent about ten minutes on a baseline plumbing run and data profiling. The next half hour implemented the candidate and diagnosed the failed reference-precomputation direction. Roughly 80 minutes then went to a 300-step candidate/control comparison and two full proxy evaluations. The remaining 80 minutes tested elapsed-time learning-rate and checkpoint machinery and ran an end-to-end candidate path. Patch review and submission took the final two minutes. The explore manifest records 11,339 phase seconds, while the submission receipt records 3,114 seconds unused; the clocks differ by 53 seconds, and this report uses the latter for the submission finding.
U-01 - Establishing the pipeline and diagnosing tied preferences
Motivation and hypothesis. The agent first needed to establish that baseline training, adapter export, and proxy scoring worked, then determine whether UltraFeedback exposed an inexpensive label-quality issue.
Concrete change and experimental setup. It ran the unmodified baseline for 20 steps on all 61,135 pairs with seed 42 and global pair batch 16, followed by a plumbing-only evaluation of the first eight proxy rows. Separately, it profiled score_chosen-score_rejected across the training shard.
Observed result. The 20-step run completed with loss 0.689805, 125.34 seconds of training, and an exported adapter. The partial evaluation was 1/8 = 0.125; the harness correctly renamed it as a partial metric, so it is not proxy evidence. The score-margin minimum was zero, and exactly 7,387 rows were ties; no negative margins were observed.
Agent interpretation. The agent treated tied rows as arbitrary directions introduced by binarization and therefore label noise. It treated the short train/eval only as plumbing.
Report assessment and confounds. The direct profile supports “7,387 ties”; although the candidate would also remove negative margins, none existed in this snapshot. No filter-only ablation was run, so the isolated IFEval effect remains unknown. The eight-row result has no scientific comparison value.
Decision and consequence. Before shuffling, the candidate selects all 53,748 rows with strictly positive score margin and passes them into trainer preprocessing; TRL can still remove fully truncated examples. Baseline loading and adapter format remain intact.