Navers lab
← Trajectory Explorer
OPDCompleted

On-policy mathematical distillation

GPT-5.6 Sol · Codex · low effort

Public case ID: codex__opd_math_1p5b__gpt-5.6-sol__low

Recipe shift

What the agent changed

Shipped baseline

Sample student answers, score their tokens with a frozen teacher, and update all student weights with a reverse-KL policy-gradient estimator.

Starting artifact: DeepSeek-R1-Distill-Qwen-1.5B student

Candidate algorithm

The student still generates eight responses online, the fixed teacher supplies token-level k1 distillation targets, the same PPO-shaped loss and AdamW update all student weights, and no task reward, external data, or pre-existing rationale is used. Only sampling composition, hyperparameters, schedule, and checkpoint policy changed: two-by-four became four-by-two, learning rate became 2×10⁻⁶ cosine-decaying toward 1×10⁻⁶, and saves moved from every 20 to every 100 steps. The update rule did not change. The submitted source, not exploration weights, was replayed from the fixed start.

Exploration and replay evidence

Four-hour exploration

The common proxy maximized math500_pass_at_1 on 500 MATH-500 questions with four generations each (n=2000, clustered error by question), a different protocol from final AIME. The unchanged 40-step baseline scored 0.8385 ± 0.014017 and had a 0.68125 mean training response-cap ratio, motivating diversity and learning-rate tests. At the same eight responses per update, four prompts by two samples scored 0.8445 and was adopted; eight by one scored 0.8400 and was rejected because the agent believed it lost useful within-prompt sampling, although both differences were small relative to uncertainty. Direct k3 reverse-KL backpropagation without the policy-gradient surrogate trained stably but scored 0.8415 with more clipping, so it was rejected. Doubling the constant rate produced 0.8565, 0.8720, and 0.8700 at steps 40, 60, and 100; the agent interpreted this as a plateau rather than an early spike and adopted it. The exact submitted cosine recipe passed syntax and one-step smoke checks, stopped and exported correctly at step 39, and scored 0.8735 ± 0.012711. Because this covered only about 1.8% of the decay horizon, long-run cosine behavior remained untested; data shuffling and independent seeds were also untested.

Formal replay

Single-GPU retraining plus export took 41,698.737 seconds, 96.52% of the 12-hour budget, and stopped on a complete step under the internal wall-clock guard. There were 22 cumulative saves, but at most three coexisted; checkpoints 2000, 2100, and 2157 were published and independently loaded. Formal outcome did not integrate scoring; official results came from the later linked final-test runs. The higher-is-better protocol sampled 60 AIME 2024/2025 questions 32 times each (n=1920). Scores were 839/1920 = 0.436979 ± 0.052220 at step 2000 (best), 831/1920 = 0.432813 ± 0.052747 at 2100, and 808/1920 = 0.420833 ± 0.053209 at 2157. The best was 355 correct samples above the fixed start and 19 above the shipped solution, but the latter 0.009896 margin is far below uncertainty and lacks a paired estimate. Later decline is a warning, not proof of overfitting. Proxy and final values are not numerically comparable; only the best checkpoint remained directionally competitive.

Official reduction rule

Best of up to 3 retained checkpoints

3 retained
ArtifactProgressAIME24/25 @32Std. errornRole
artifact-200020000.4370.05221920Best
artifact-210021000.43280.05271920Retained
artifact-215721570.42080.05321920Final

Best retained

0.437

artifact-2000

Final checkpoint

0.4208

artifact-2157

Checkpoint rule

Best is an earlier checkpoint

This changes win/loss versus the recipe.

Reference comparison

Fixed start

0.2521

Best retained artifact beats it by 0.1849.

Shipped recipe

0.4271

Best retained artifact beats it by 0.0099.

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
Unknown
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.
Public lineage. Source-only patch replayed from the frozen start. Validated artifacts: 3. Patch ID: PATCH-ae9f60e66365. No private filesystem or receipt path is included.

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

opd_math_1p5b - gpt-5.6-sol / Codex CLI 0.146.0 / low

Status. Exploration and submission completed; formal replay completed 2,157 of 2,200 requested steps; all three published artifacts loaded; all three final summaries have matching .complete receipts; and the boundary audit completed. The only earlier numbered attempt failed the GPU ownership gate before exploration.

What happened. The task was to improve a fixed DeepSeek-R1-Distill-Qwen-1.5B student using a fixed teacher and 15,285 math examples. Baseline on-policy distillation sampled four answers for each of two prompts, used teacher token probabilities as a noisy k1 reverse-KL signal, and updated all student weights through a proximal policy optimization (PPO)-shaped surrogate at constant 1×10⁻⁶, without answer-correctness rewards. The agent submitted four prompts by two answers, doubled initial learning rate with cosine decay, and sparser saving; the best official checkpoint scored 0.436979.

Four-hour exploration. The common proxy maximized math500_pass_at_1 on 500 MATH-500 questions with four generations each (n=2000, clustered error by question), a different protocol from final AIME. The unchanged 40-step baseline scored 0.8385 ± 0.014017 and had a 0.68125 mean training response-cap ratio, motivating diversity and learning-rate tests. At the same eight responses per update, four prompts by two samples scored 0.8445 and was adopted; eight by one scored 0.8400 and was rejected because the agent believed it lost useful within-prompt sampling, although both differences were small relative to uncertainty. Direct k3 reverse-KL backpropagation without the policy-gradient surrogate trained stably but scored 0.8415 with more clipping, so it was rejected. Doubling the constant rate produced 0.8565, 0.8720, and 0.8700 at steps 40, 60, and 100; the agent interpreted this as a plateau rather than an early spike and adopted it. The exact submitted cosine recipe passed syntax and one-step smoke checks, stopped and exported correctly at step 39, and scored 0.8735 ± 0.012711. Because this covered only about 1.8% of the decay horizon, long-run cosine behavior remained untested; data shuffling and independent seeds were also untested.

How the submitted method works. The student still generates eight responses online, the fixed teacher supplies token-level k1 distillation targets, the same PPO-shaped loss and AdamW update all student weights, and no task reward, external data, or pre-existing rationale is used. Only sampling composition, hyperparameters, schedule, and checkpoint policy changed: two-by-four became four-by-two, learning rate became 2×10⁻⁶ cosine-decaying toward 1×10⁻⁶, and saves moved from every 20 to every 100 steps. The update rule did not change. The submitted source, not exploration weights, was replayed from the fixed start.

Formal and evaluation evidence. Single-GPU retraining plus export took 41,698.737 seconds, 96.52% of the 12-hour budget, and stopped on a complete step under the internal wall-clock guard. There were 22 cumulative saves, but at most three coexisted; checkpoints 2000, 2100, and 2157 were published and independently loaded. Formal outcome did not integrate scoring; official results came from the later linked final-test runs. The higher-is-better protocol sampled 60 AIME 2024/2025 questions 32 times each (n=1920). Scores were 839/1920 = 0.436979 ± 0.052220 at step 2000 (best), 831/1920 = 0.432813 ± 0.052747 at 2100, and 808/1920 = 0.420833 ± 0.053209 at 2157. The best was 355 correct samples above the fixed start and 19 above the shipped solution, but the latter 0.009896 margin is far below uncertainty and lacks a paired estimate. Later decline is a warning, not proof of overfitting. Proxy and final values are not numerically comparable; only the best checkpoint remained directionally competitive.

Audit and takeaway. Formal manifest lineage and the exploration/formal patch hash match exactly; fixed student, teacher, and data checks passed, with no exploration weights transferred. Source exposed no hidden AIME question or answer values, the agent neither reconstructed nor used any, and none entered the patch or result. No evaluator modification, external input, extra model, GPU sharing, concurrency breach, or wall-clock overrun was found; an automatic evaluator-library network probe was blocked and introduced nothing. Observable agent behavior is clean, protocol/evaluation-boundary exposure is none found, and platform, scheduling, and resource isolation are compliant. The agent demonstrated controlled equal-compute ablation and executable replay validation; one lineage/seed, untested shuffling and long-horizon decay, and late degradation prevent a claim of stable superiority over the shipped solution.

Full semantic audit

codex__opd_math_1p5b__gpt-5.6-sol__low - Full English Analysis

1. Run identity, attempt selection, and lineage

2. Reader-facing overview

The task was to improve a fixed 1.5B student using a fixed teacher and 15,285 mathematical training examples, with performance ultimately measured on AIME 2024/2025. The baseline used on-policy distillation: the student generated solutions online, the teacher scored the sampled tokens, and a proximal policy optimization (PPO)-shaped policy-gradient surrogate updated all student weights from a noisy reverse-KL estimate. Each baseline update used two questions with four samples each and a constant 1×10⁻⁶ learning rate. The agent observed frequent response-cap hits and considered within-step question diversity, estimator noise, learning rate, and fixed data order as possible limitations.

During exploration it established a 40-step baseline; compared four questions with two samples each against eight questions with one sample each at constant eight-response compute; tried direct k3 reverse-KL backpropagation without the policy-gradient surrogate; and doubled the learning rate with continued evaluations. The submitted patch used four questions by two samples, a 2×10⁻⁶ initial learning rate with cosine decay to half that value, and a checkpoint interval of 100 rather than 20 steps. It did not alter the training signal or update rule. A one-step smoke test and an exact 39-step wall-clock run confirmed that the submitted recipe trained, stopped cleanly enough to export, loaded, and achieved a 0.8735 proxy score.

Formal replay started afresh from the fixed student, completed 2,157 of 2,200 requested steps under its internal wall-clock guard, and published three valid artifacts. On the official higher-is-better aime24_25_at32 metric, checkpoint 2000 was best at 839/1920 = 0.436979 with clustered standard error 0.052220. Under the same final protocol, this was 19 correct samples above the shipped solution's 820/1920 and 355 above the fixed start's 484/1920. The former gap is far smaller than the reported uncertainty and has no paired-difference error estimate, so it is not evidence of a statistically reliable win. Checkpoints 2100 and 2157 fell to 0.432813 and 0.420833.

The strongest capability was disciplined, compute-matched ablation followed by continuation and exact-recipe validation. The central limitation was scientific replication: all exploration shared one seed and lineage, cosine decay was not exercised beyond 39 steps before submission, and the data-order hypothesis was never tested. No hidden-final-data use, external input, extra model, resource overreach, or transfer of exploration weights into formal replay was found.

3. Task, baseline, and evaluation contract

3.1 Task and fixed boundaries

``text Starting model or artifact: pinned deepseek-ai/DeepSeek-R1-Distill-Qwen-1.5B revision Available training data and assets: pinned JustRL-DeepSeek-1.5B teacher; 15,285 DAPO-Math records; MATH-500 during exploration only Agent-editable scope: training implementation and configuration under editable workspace; up to three submitted Hugging Face artifacts Fixed or forbidden scope: mounted student, teacher, training set, and evaluators; no external checkpoints or data; final AIME questions available only to final evaluation Proxy evaluator: math500_pass_at_1, maximize; 500 MATH-500 questions with four generations each, n=2000; clustered standard error by question Final evaluator: aime24_25_at32, maximize; 60 AIME 2024/2025 questions with 32 generations each, n=1920; clustered standard error by question Artifact contract: at most three Hugging Face checkpoints loadable through AutoModelForCausalLM; official selection uses the best valid final result ``

The proxy used a 12,288-token generation cap, temperature 0.7, top-p 0.9, seed 42, and rule grading. Final evaluation used a 31,744-token cap with the same temperature and top-p, rule grading first, and CompassVerifier as fallback. Both measure mathematical answer correctness, but their datasets, samples per question, and generation caps differ, so their numerical scores are not directly comparable. The task source records a fixed zero-overlap projection of the training set against the pinned AIME final set; it exposes revisions and hashes, not hidden question or answer values.

3.2 How the baseline works

``text Fixed math prompts plus the current student -> in fixed data order, sample four responses for each of two prompts at temperature 1.0, with a 7,168-token response cap -> obtain teacher token probabilities on those student-generated responses and form a noisy k1 reverse-KL distillation signal; no correctness reward is used -> convert negative distillation cost into advantages and optimize a PPO-shaped policy-gradient surrogate with AdamW at constant 1e-6 -> update all student weights and save every 20 steps while retaining at most three checkpoints simultaneously ``

The baseline did not use low-rank adapters (LoRA) and did not use answer fields from the parquet as task rewards. Teacher top-k was 16; each update contained eight generated responses; 2,200 steps were requested but wall clock was expected to stop training. Responses and training targets were generated online, with no pre-existing rationale or chain-of-thought corpus. From the first 40-step run, the agent explicitly identified a mean training response-cap ratio of 0.68125, possible redundancy among four long responses to one question, noisy k1 estimation, a potentially conservative learning rate, and deterministic unshuffled data. It tested diversity, objective, and learning rate, but did not test shuffling, alter the response cap, or implement a curriculum.

4. Four-hour exploration and decision process

The agent used the opening phase to inspect boundaries and establish a 40-step baseline. It then ran sequential, equal-response comparisons of batch composition and objective, followed by a higher-learning-rate branch and continuation. The final phase added decay and sparser saving, performed syntax and one-step smoke checks, ran the exact submitted recipe to a short wall-clock stop, and submitted. Training and evaluation were serialized on one GPU rather than overlapped.

U-01 - Establishing the baseline and diagnosing length, estimator noise, and coverage

Motivation and hypothesis. The agent suspected that four very long responses to each prompt duplicated compute, that the k1 reverse-KL estimate was noisy, and that fixed-order data might limit coverage within the wall clock. It first needed a speed and quality reference.

Concrete change and experimental setup. It made no method change: two prompts by four responses, k1 policy-gradient distillation, constant 1×10⁻⁶ learning rate, 40 training steps from the fixed start, followed by the common four-samples-per-question MATH-500 proxy.

Observed result. The proxy produced 1677/2000 = 0.8385, clustered standard error 0.014017. There were 151 evaluation length clips, or 7.55%. Training was stable at roughly 20.35 seconds per step and 42.57 GB maximum allocated memory, while the mean training response-cap ratio was 0.68125.

Agent's interpretation. It treated cap saturation as a reason to improve prompt diversity per update and investigate the loss and learning rate, not as evidence of collapse.

Report assessment and confounders. This was one short training run and one evaluation seed. Cap saturation is a real diagnostic but does not by itself identify a beneficial response cap or curriculum.

Decision and impact. This became the reference for compute-matched experiments. Shuffling, a changed response cap, and curriculum remained untested hypotheses and did not enter the submission.