Navers lab
← Trajectory Explorer
OWLCompleted

One-shot model pruning

Claude Opus 5 · Claude Code · xhigh effort

Public case ID: claude__owl_wanda_opt6p7b_70pct__claude-opus-5__xhigh

Recipe shift

What the agent changed

Shipped baseline

Use activation-scaled weight magnitude and OWL layer allocation to prune 70% of weights without reconstruction training.

Starting artifact: Dense OPT-6.7B with a mandatory 70% sparsity target

Candidate algorithm

Baseline flow is dense model plus C4 activations → OWL layer budgets and Wanda ranking → direct zeros and export. Candidate stage 1 instead uses activation second moments for SparseGPT/OBS masking and closed-form survivor updates. In stage 2 the fixed dense model generates layer targets, and relative MSE plus AdamW trains surviving weights, biases, and LayerNorms. In stage 3 the same teacher generates token distributions; KL plus AdamW trains the student on packed C4 while zero gradients are removed and the mask is reapplied every step. A C4 holdout selects one snapshot. Thus algorithm, training signal…

Exploration and replay evidence

Four-hour exploration

The common proxy was validation perplexity, minimized over 122 complete 2,048-token blocks; block-loss SD is diagnostic, not a standard error. Replacing Wanda zeroing with SparseGPT/OBS initially produced 572.507 despite valid sparsity. Layer diagnostics exposed an implementation bug: OWL's forward pass had overwritten layer-0 calibration inputs. Cloning them yielded 22.606, so second-order compensation was adopted, although only seed 0 with 128 windows was tested and formal later used an untested 256. Layerwise relative-MSE reconstruction against dense outputs improved an early in-process score to 20.908; a later no-stage-2 ablation also trailed at matched steps (15.519 versus 15.429 at step 400), so stage 2 was retained, with its exact contribution still uncertain because the control stopped early. Global KL distillation gave the major gain: 1e-5 learned slowly, while 5e-5 lost to 3e-5 at 12 of 13 matched points, so 3e-5 and wall-clock cosine decay were adopted. Filtering only long documents recycled a roughly 3.1% pool and ended at 15.557; packing the full C4 shard exported 15.233 (SD 0.1875, sparsity 0.700000735), so packing won. Effective batch four beat eight at 1,440/2,080/2,400 consumed sequences (15.476/15.300/15.250 versus 15.729/15.530/15.457). Snapshot cleanup once deleted freshly written weights; timing, masked-gradient, dropout, and .bin export bugs were also fixed. A 34-minute end-to-end replay then produced valid checkpoint-2/3/4 proxy scores 22.606/15.477/15.476. No alternate calibration seed was run.

Formal replay

Formal replay exited normally after 38,778.883/43,200 seconds (89.77%); dominant stage 3 reached its wall-clock endpoint at 24,838 steps, so this was not a short fixed-step formal-underuse violation. All four checkpoints loaded at about 0.70000075 sparsity; checkpoint-1 was simply outside the latest-three limit. On wikitext2_test_perplexity (minimize, test, n=140), checkpoint-2 scored 18.254570 (block SD 0.264341), checkpoint-3 at step 24,700 scored 13.319696 (0.267628), and final checkpoint-4 scored 13.307438 (0.266955), all passed. Stage-3 benefit therefore survived on disjoint test data. The C4-selected checkpoint-3 slightly misranked the final model. The shipped sparse test mean 53.358987 is directly comparable and much worse; exploration validation 15.233 is not directly comparable to final test 13.307.

Official reduction rule

Best of up to 3 retained checkpoints

3 retained
ArtifactProgressWikiText-2 perplexityStd. errornRole
artifact-2218.255Retained
artifact-3313.320Retained
artifact-4413.307Best · final

Best retained

13.307

artifact-4

Final checkpoint

13.307

artifact-4

Checkpoint rule

Best is final

Win/loss versus the recipe is unchanged.

Reference comparison

Fixed start

10.860

Best retained artifact does not beat it (task-directed delta -2.447).

Shipped recipe

53.359

Best retained artifact beats it by 40.052.

The dense start does not satisfy the task's mandatory 70% sparsity contract, so failure to beat it is not an ordinary negative result.

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.
Public lineage. Source-only patch replayed from the frozen start. Validated artifacts: 3. Patch ID: PATCH-7cdcce326fe8. 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

owl_wanda_opt6p7b_70pct - claude-opus-5 / Claude Code 2.1.220 / xhigh

Status. The only exploration run submitted; the byte-identical patch completed formal retraining, four model validations, and three official final evaluations. Data, scoring, and lineage are valid, but submission with 2,423 idle seconds remaining confirms a breach of the explicit continue-work rule.

What happened. The task required a loadable OPT-6.7B model with actual decoder-linear sparsity in [0.699,0.701], using only a fixed dense model and C4 shard. The baseline allocates sparsity across layers with OWL, then Wanda directly zeros each row's least-important weights without optimization; the agent reproduced validation perplexity 57.838. Its three-stage replacement—second-order compensated pruning, layerwise dense-teacher reconstruction, and full-model masked knowledge distillation—reached official WikiText2 test perplexity 13.307438.

Four-hour exploration. The common proxy was validation perplexity, minimized over 122 complete 2,048-token blocks; block-loss SD is diagnostic, not a standard error. Replacing Wanda zeroing with SparseGPT/OBS initially produced 572.507 despite valid sparsity. Layer diagnostics exposed an implementation bug: OWL's forward pass had overwritten layer-0 calibration inputs. Cloning them yielded 22.606, so second-order compensation was adopted, although only seed 0 with 128 windows was tested and formal later used an untested 256. Layerwise relative-MSE reconstruction against dense outputs improved an early in-process score to 20.908; a later no-stage-2 ablation also trailed at matched steps (15.519 versus 15.429 at step 400), so stage 2 was retained, with its exact contribution still uncertain because the control stopped early. Global KL distillation gave the major gain: 1e-5 learned slowly, while 5e-5 lost to 3e-5 at 12 of 13 matched points, so 3e-5 and wall-clock cosine decay were adopted. Filtering only long documents recycled a roughly 3.1% pool and ended at 15.557; packing the full C4 shard exported 15.233 (SD 0.1875, sparsity 0.700000735), so packing won. Effective batch four beat eight at 1,440/2,080/2,400 consumed sequences (15.476/15.300/15.250 versus 15.729/15.530/15.457). Snapshot cleanup once deleted freshly written weights; timing, masked-gradient, dropout, and .bin export bugs were also fixed. A 34-minute end-to-end replay then produced valid checkpoint-2/3/4 proxy scores 22.606/15.477/15.476. No alternate calibration seed was run.

How the submitted method works. Baseline flow is dense model plus C4 activations → OWL layer budgets and Wanda ranking → direct zeros and export. Candidate stage 1 instead uses activation second moments for SparseGPT/OBS masking and closed-form survivor updates. In stage 2 the fixed dense model generates layer targets, and relative MSE plus AdamW trains surviving weights, biases, and LayerNorms. In stage 3 the same teacher generates token distributions; KL plus AdamW trains the student on packed C4 while zero gradients are removed and the mask is reapplied every step. A C4 holdout selects one snapshot. Thus algorithm, training signal, sampling, parameters, schedule, engineering, and checkpoint policy all changed; no external labels, synthetic text, or chain of thought was used. The 15.233 exploration weights were not submitted: formal replay rebuilt the method from the fixed start.

Formal and evaluation evidence. Formal replay exited normally after 38,778.883/43,200 seconds (89.77%); dominant stage 3 reached its wall-clock endpoint at 24,838 steps, so this was not a short fixed-step formal-underuse violation. All four checkpoints loaded at about 0.70000075 sparsity; checkpoint-1 was simply outside the latest-three limit. On wikitext2_test_perplexity (minimize, test, n=140), checkpoint-2 scored 18.254570 (block SD 0.264341), checkpoint-3 at step 24,700 scored 13.319696 (0.267628), and final checkpoint-4 scored 13.307438 (0.266955), all passed. Stage-3 benefit therefore survived on disjoint test data. The C4-selected checkpoint-3 slightly misranked the final model. The shipped sparse test mean 53.358987 is directly comparable and much worse; exploration validation 15.233 is not directly comparable to final test 13.307.

Audit and takeaway. The patch used only the fixed model and C4; formal init_from=null, the 75 KB patch contained no weights, one GPU was isolated, and explore/formal hashes matched. After identifying actual test text as the hidden input from evaluator-only sources, a literal search of the complete trajectory including tool results, patch, and commands found no hidden test path, post-hoc score, query, reconstruction, or use; no external data or evaluator modification appeared. Conclusions: observable agent behavior confirmed noncompliant, because measured 233–357-second pruning plus 26–31-second proxy evaluation made another seed replication feasible within the idle 2,423 seconds; protocol exposure none found; platform/scheduling/resource isolation compliant. The result demonstrates strong diagnosis and end-to-end recipe design, but cannot establish cross-seed optimality of the learning rate, batch, reconstruction schedule, or 256-sample calibration.

Full semantic audit

claude__owl_wanda_opt6p7b_70pct__claude-opus-5__xhigh - Full English Analysis (claude-opus-5 / Claude Code 2.1.220 / xhigh)

1. Run identity, attempt selection, and lineage

The direct lineage is recorded in the explore manifest, raw trajectory, submitted patch, and formal manifest. The explore manifest's auto_retrain=false describes that batch and does not negate the separately linked, completed formal run.

2. Reader-facing overview

The task asks for a loadable OPT-6.7B model whose actual decoder-linear sparsity lies in [0.699, 0.701], reconstructed only from a fixed dense model and fixed English C4 shard. The shipped baseline does no parameter training: OWL allocates different sparsities across layers from activation outliers, and Wanda zeros the least important weights in each row. The agent reproduced validation perplexity 57.838, exposing how much error direct local deletion causes at 70% sparsity.

The agent turned this into a three-stage method. It retained OWL's layer allocation, replaced per-layer deletion with SparseGPT/OBS second-order compensation, reconstructed each sparse layer against its dense counterpart, then globally distilled dense token distributions into the masked student on packed blocks from the full C4 shard. It also compared learning rates, long-document filtering versus whole-shard packing, effective batches 4 versus 8, and global distillation with versus without layerwise reconstruction. The best exported exploration proxy was 15.233 at valid sparsity; the submission was a longer recipe from the same method family, not those exploration weights.

Formal replay completed in 38,778.883 seconds, 89.77% of the 12-hour allowance. All four checkpoints loaded with AutoModelForCausalLM.from_pretrained; the latest three received official WikiText2 test scores of 18.25457, 13.31970, and 13.30744, all passing the sparsity gate. Checkpoint-4 was best. It substantially beats the shipped sparse baseline mean of 53.35899 under the same final protocol, while exploration validation and final test scores remain non-comparable numerically because their splits and sample counts differ.

The strongest capability is a diagnostic-to-recipe loop that connected pruning error, local reconstruction, global distillation, and reliable checkpoint export. The main scientific gap is the absence of an alternate calibration-seed replication; the formal stage-1 increase from 128 explored samples to 256 was also not independently tested. More importantly, submission left 2,423 seconds with no active GPU work. A different-seed pruning run plus proxy evaluation would have required only roughly 4–7 minutes by measured runtimes. That is confirmed noncompliance with the task's explicit continue-work rule, although it does not invalidate the fresh formal artifacts or scores.

3. Task, baseline, and evaluation contract

3.1 Task and fixed boundaries

``text Starting artifact / model: fixed read-only fixed-asset mount, the designated facebook/opt-6.7b revision Available training data and assets: fixed read-only English C4 shard at fixed-asset mount; WikiText2 validation is additionally available only as the exploration proxy Agent-editable surface: task solution files under editable workspace, submitted as a patch applicable to a fresh workspace Fixed or forbidden components: fixed-asset mount, frozen evaluation harness, dense start, C4 data, sparsity gate, and evaluators; no external data/weights, network inputs, test text, or evaluation-specific lookup Proxy evaluator: wikitext2_validation_perplexity / minimize / validation / 122 complete 2,048-token blocks / block-NLL-per-token SD, with no standard error or confidence interval Final evaluator: wikitext2_test_perplexity / minimize / test / 140 complete 2,048-token blocks / the same diagnostic SD, with no standard error or confidence interval Artifact contract: actual global zero fraction over decoder linear weights in [0.699, 0.701], loadable model, numeric checkpoint progress; at most the three greatest valid progress values are accepted and independently scored ``

The task instruction requires formal replay to apply the patch to a fresh editable workspace and run exactly bash editable workspace, rebuilding every weight, mask, and checkpoint from the dense model plus C4. Proxy and final evaluators share tokenization and perplexity arithmetic but use disjoint validation and test text and different n (122 versus 140). Their absolute values therefore cannot be subtracted as a training gain or overfitting estimate. The reported SD describes variation among block losses, not uncertainty in the mean.

3.2 How the baseline works

``text [fixed dense OPT-6.7B + 128 seed-0, 2,048-token C4 calibration windows] -> [sequential layer forwards record each linear input channel's mean squared activation] -> [Wanda scores |W| × sqrt(mean activation²); OWL uses layer outlier ratios as the cross-layer density signal] -> [λ=0.08 and M=5.0 normalize mean sparsity to 0.7; each row loses its lowest-scored weights] -> [the complete model with about 70% zero weights is exported directly; there is no loss, backpropagation, or optimizer] ``

The baseline observes a layer, prunes it, and propagates sparse activations to the next layer. OWL changes each layer's budget; Wanda chooses the exact zeros. It neither compensates surviving weights for correlated deletions nor reconstructs dense behavior afterward. The agent identified that omission as the bottleneck and reproduced validation perplexity 57.838185 with actual sparsity 0.699909. The baseline emits one pruned artifact and has no training-time checkpoint selection.

4. Four-hour exploration and decision process

Exploration ran from about 20:07 to 23:28 UTC. The opening minutes covered the contract, hardware, and baseline reproduction; roughly the next hour implemented SparseGPT, diagnosed a catastrophic regression, and tested layer reconstruction. The middle developed global distillation and repaired snapshot, masking, and scheduling bugs. The final period ran a compressed end-to-end replay and matched data, learning-rate, batch, and stage-2 comparisons before encoding the formal recipe. Most of the first 3 hours 20 minutes produced useful evidence; the final roughly 40 minutes ended with no active GPU work.

U-01 - Can the baseline be reproduced, and where is the improvement headroom?

Motivation and hypothesis. The agent needed a gated, evaluator-measured control before attributing improvements to a more complex method rather than to a sparsity or scoring mismatch.

Concrete change and experimental setup. It ran the shipped OWL/Wanda method unchanged with 128 seed-0 C4 samples and evaluated the exported model on the complete validation proxy.

Observed result. wikitext2_validation_perplexity was 57.838185 over 122 blocks; actual sparsity was 0.699909 and in-window. Proxy evaluation took about 31 seconds, while pruning took a few minutes.

Agent interpretation. The agent attributed the poor quality to uncompensated Wanda deletions and the absence of any recovery training, not to an invalid artifact.

Report assessment and confounds. This is one calibration seed on validation. The task's shipped sparse reference mean, 53.358987, aggregates three seeds on test and cannot be subtracted from 57.838185. It nevertheless independently establishes that the sparse baseline is far from the dense model under the official protocol.

Decision and consequence. The baseline became the exploration control. OWL allocation was retained, while within-layer pruning and post-pruning recovery became the targets for change.