Navers lab
← Trajectory Explorer
OWLCompleted

One-shot model pruning

Claude Sonnet 5 · Claude Code · high effort

Public case ID: claude__owl_wanda_opt6p7b_70pct__claude-sonnet-5__high

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: dense OPT and C4 activations - OWL sparsity allocation - Wanda ranking and direct zeroing - one-shot sparse model. Candidate flow: the same fixed start and 128 seed-0 C4 windows - uniform SparseGPT estimates an activation Hessian and compensates surviving weights during pruning - seed-1000 C4 windows provide next-token labels - AdamW minimizes causal cross entropy over all parameters. Masks on 192 decoder linear layers suppress gradients at pruned locations and re-zero them after every step; other weights, embeddings, head, biases, and layer norms can change. No external model, synthetic labels…

Exploration and replay evidence

Four-hour exploration

The proxy was lower-is-better wikitext2_validation_perplexity on 122 disjoint validation blocks of 2,048 tokens; block-NLL standard deviation is dispersion, not standard error. First, the agent measured OWL/Wanda at 57.8382 and repaired a LLaMA-specific position-argument incompatibility before SparseGPT could run on OPT. Second, OWL-allocated SparseGPT scored 22.6944, while uniform per-layer SparseGPT scored 21.3580 and ran faster; the agent attributed the dominant gain to reconstruction compensation and adopted uniform allocation. This comparison used only calibration seed 0. A patch note claims a uniform-Wanda result, but no raw run supports it.

Third, fixed-mask next-token training reduced 21.3580 to 17.4839 after 14 steps. Repeated moderate runs at learning rate 3e-5, microbatch 4, and accumulation 2 continued to 15.2972 after 634 steps/1,775 seconds, with sparsity unchanged and no nonfinite steps; the agent adopted this branch. Fourth, a 6e-5/microbatch-8/accumulation-1/seed-2000 alternative—with the same effective batch—reached only 15.6299 at 306 steps, so only that confounded combination was rejected. Fine-tuning from the OWL allocation scored 16.3965 at 169 steps and was also rejected. Two memory probes were intentionally killed without scores; seeing no plain-loss plateau, the agent considered but did not implement distillation.

Finally, an 1,800-second end-to-end run reproduced fresh pruning and 205 fine-tune steps, improving 21.3580 to 15.4159 and validating wall-clock/export behavior. However, the agent tested neither a second calibration seed nor more than 128 calibration samples despite fixing the buffer to permit it. One prune plus evaluation took roughly six minutes, so such work fit the remaining 1:22. Short exploration runs supported the method, but not the later assumption that quality would improve throughout formal training.

Formal replay

Formal replay used a 43,200-second outer budget; orchestrator and candidate reserves yielded 41,476 fine-tune seconds. It stopped normally after 16,681 optimizer steps and 41,416.8 fine-tune seconds, with zero skipped steps. Progress labels 1–24 were cumulatively published, but only the latest three were simultaneously retained. Checkpoints 22/23/24 all loaded and passed sparsity near 0.70000064. Their official test perplexities (n=140) were 21.677989, 21.892863, and 22.116346; block-NLL SDs were 0.264457, 0.261074, and 0.259587. Checkpoint 22 is best, and two successive degradations show late-training risk. Proxy and final splits are disjoint and their scores cannot be subtracted. Because earlier states were deleted, checkpoint 22 cannot be called globally best over the full run.

Official reduction rule

Best of up to 3 retained checkpoints

3 retained
ArtifactProgressWikiText-2 perplexityStd. errornRole
artifact-222221.678Best
artifact-232321.893Retained
artifact-242422.116Final

Best retained

21.678

artifact-22

Final checkpoint

22.116

artifact-24

Checkpoint rule

Best is an earlier checkpoint

Win/loss versus the recipe is unchanged.

Reference comparison

Fixed start

10.860

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

Shipped recipe

53.359

Best retained artifact beats it by 31.681.

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-1df2a9b7eb6a. 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-sonnet-5 / Claude Code 2.1.220 / high

Status. Exploration, submission, formal retraining, three artifact validations, and three final evaluations completed; every final summary has its .complete receipt. Data/model lineage and formal replay were compliant, but submitting with 4,935 seconds and feasible experiments remaining makes observable behavior confirmed for early termination.

What happened. The task asks for a loadable, approximately 70%-unstructured-sparse OPT-6.7B from fixed dense weights and fixed C4. The baseline uses OWL to allocate layer sparsity and Wanda to zero weights ranked by magnitude and activation, with no error compensation or fine-tuning. The agent submitted uniform SparseGPT—second-order, layerwise error-compensated pruning—followed by mask-preserving C4 language-model fine-tuning. Best formal checkpoint 22 achieved 21.677989 WikiText2 test perplexity versus the shipped sparse three-seed mean of 53.358987 under the same final protocol.

Four-hour exploration. The proxy was lower-is-better wikitext2_validation_perplexity on 122 disjoint validation blocks of 2,048 tokens; block-NLL standard deviation is dispersion, not standard error. First, the agent measured OWL/Wanda at 57.8382 and repaired a LLaMA-specific position-argument incompatibility before SparseGPT could run on OPT. Second, OWL-allocated SparseGPT scored 22.6944, while uniform per-layer SparseGPT scored 21.3580 and ran faster; the agent attributed the dominant gain to reconstruction compensation and adopted uniform allocation. This comparison used only calibration seed 0. A patch note claims a uniform-Wanda result, but no raw run supports it.

Third, fixed-mask next-token training reduced 21.3580 to 17.4839 after 14 steps. Repeated moderate runs at learning rate 3e-5, microbatch 4, and accumulation 2 continued to 15.2972 after 634 steps/1,775 seconds, with sparsity unchanged and no nonfinite steps; the agent adopted this branch. Fourth, a 6e-5/microbatch-8/accumulation-1/seed-2000 alternative—with the same effective batch—reached only 15.6299 at 306 steps, so only that confounded combination was rejected. Fine-tuning from the OWL allocation scored 16.3965 at 169 steps and was also rejected. Two memory probes were intentionally killed without scores; seeing no plain-loss plateau, the agent considered but did not implement distillation.

Finally, an 1,800-second end-to-end run reproduced fresh pruning and 205 fine-tune steps, improving 21.3580 to 15.4159 and validating wall-clock/export behavior. However, the agent tested neither a second calibration seed nor more than 128 calibration samples despite fixing the buffer to permit it. One prune plus evaluation took roughly six minutes, so such work fit the remaining 1:22. Short exploration runs supported the method, but not the later assumption that quality would improve throughout formal training.

How the submitted method works. Baseline flow: dense OPT and C4 activations -> OWL sparsity allocation -> Wanda ranking and direct zeroing -> one-shot sparse model. Candidate flow: the same fixed start and 128 seed-0 C4 windows -> uniform SparseGPT estimates an activation Hessian and compensates surviving weights during pruning -> seed-1000 C4 windows provide next-token labels -> AdamW minimizes causal cross entropy over all parameters. Masks on 192 decoder linear layers suppress gradients at pruned locations and re-zero them after every step; other weights, embeddings, head, biases, and layer norms can change. No external model, synthetic labels, reward, or chain-of-thought is used. This changes the pruning algorithm, training signal, trainable parameters, schedule, engineering, and checkpoint policy. Exploration weights did not cross into formal replay.

Formal and evaluation evidence. Formal replay used a 43,200-second outer budget; orchestrator and candidate reserves yielded 41,476 fine-tune seconds. It stopped normally after 16,681 optimizer steps and 41,416.8 fine-tune seconds, with zero skipped steps. Progress labels 1–24 were cumulatively published, but only the latest three were simultaneously retained. Checkpoints 22/23/24 all loaded and passed sparsity near 0.70000064. Their official test perplexities (n=140) were 21.677989, 21.892863, and 22.116346; block-NLL SDs were 0.264457, 0.261074, and 0.259587. Checkpoint 22 is best, and two successive degradations show late-training risk. Proxy and final splits are disjoint and their scores cannot be subtracted. Because earlier states were deleted, checkpoint 22 cannot be called globally best over the full run.

Audit and takeaway. Fixed C4/model use, evaluator integrity, no external inputs, fresh replay, single-GPU isolation, wall clock, and patch hash were verified. No hidden final value reached the trajectory, was reconstructed or used, or affected the patch/result. Observable behavior is confirmed only for the explicit early-submission breach; protocol/evaluation-boundary exposure was not found, and platform/scheduling/resource isolation was compliant. The case demonstrates strong algorithm-to-replay engineering and a genuine sparse-baseline improvement, but not seed robustness, monotonic benefit from longer training, or optimal checkpoint coverage.

Full semantic audit

claude__owl_wanda_opt6p7b_70pct__claude-sonnet-5__high - Full English Analysis

1. Run identity, attempt selection, and lineage

The exploration task files and the formal-source task files are byte-identical. The formal control spec fixes the selected-exploration lineage, source commit, task hashes, and exact patch hash. Formal results therefore have verified lineage to this submission rather than to a similarly named directory or an exploration-time model.

2. Reader-facing overview

The task is to construct a loadable, approximately 70%-unstructured-sparse OPT-6.7B model from a fixed dense model and fixed C4 calibration asset while minimizing WikiText2 perplexity. The shipped baseline uses OWL to allocate different sparsities across layers and Wanda's weight-magnitude/activation score to zero weights. It performs neither reconstruction-error compensation nor fine-tuning; its measured validation perplexity in exploration was 57.8382.

The agent first repaired an OPT incompatibility in SparseGPT, a layerwise approximate-second-order method that compensates surviving weights for pruning error, then compared OWL allocation against uniform per-layer sparsity. Uniform SparseGPT scored 21.3580 on the proxy, better than OWL-allocated SparseGPT at 22.6944. It then added mask-preserving C4 language-model fine-tuning: pruned positions in 192 decoder linear layers were re-zeroed after every update, while unpruned weights and the rest of the model could train. The moderate-learning-rate branch reached 15.2972 in the longest 30-minute exploration run. A higher-learning-rate/larger-microbatch combination and fine-tuning from the OWL allocation were worse, so the submission was uniform SparseGPT followed by moderate sparse fine-tuning.

Formal replay rebuilt everything from the fixed dense model, completed 16,681 optimizer steps, cumulatively published progress labels 1 through 24, and simultaneously retained only three checkpoints. Checkpoints 22–24 all loaded and passed the final sparsity gate. Their test perplexities were 21.6780, 21.8929, and 22.1163, making checkpoint 22 the official best under the lower-is-better rule. It substantially beat the shipped sparse baseline's same-protocol three-seed mean of 53.3590, although it remained worse than the ineligible dense reference of 10.8605.

The principal capability was identifying a better high-sparsity reconstruction algorithm and integrating it with truly mask-preserving training, wall-clock control, export, and load validation. The main scientific weakness was latest-only checkpoint retention: all three final scores worsened with additional late training, while potentially better mid-run states had already been deleted. Calibration-seed robustness, explicitly highlighted by the task, was never tested. There was also a clear execution-protocol breach: the agent explicitly submitted with 4,935 seconds remaining even though a calibration-size or calibration-seed experiment could have completed. Observable agent behavior is therefore confirmed, specifically for early termination; this does not invalidate the formally replayed models or their final scores.

3. Task, baseline, and evaluation contract

3.1 Task and fixed boundary

``text Starting model or artifact: fixed dense OPT-6.7B at fixed-asset mount Available training data / assets: fixed English C4 training shard and validation file; WikiText2 validation was available only for exploration evaluation Agent-editable surface: candidate implementation, training method, hyperparameters, schedule, and checkpoint policy under editable workspace Fixed or forbidden surface: starting model and mounted assets, evaluation harness, 70% sparsity gate, final test data; no network, external data, or external weights Proxy evaluator: wikitext2_validation_perplexity / minimize / WikiText2 validation / 122 blocks of length 2048 / per-block token-NLL standard deviation as a dispersion diagnostic Final evaluator: wikitext2_test_perplexity / minimize / WikiText2 test / 140 blocks of length 2048 / the same dispersion diagnostic Artifact contract: a standard-loadable OPT causal LM with decoder zero fraction in [0.699, 0.701]; up to three valid formal artifacts are accepted and the best final metric wins ``

Both evaluators split contiguous text into 2,048-token blocks and aggregate token negative log likelihood into perplexity, but they use disjoint validation and test splits and different block counts. Comparisons within a protocol are valid; subtraction of an exploration proxy score from a final score is not. The reported block-NLL standard deviation describes heterogeneity among text blocks. It is neither a standard error nor a confidence interval.

The task provides same-final-protocol sparse references of 53.997456, 52.617988, and 53.461515, with declared mean 53.358987. These are valid final comparisons. The dense reference is 10.860456, but it has zero sparsity and is only a quality bound, not an eligible competitor.

3.2 How the baseline works

``text Fixed dense OPT-6.7B plus 128 C4 calibration sequences at seed 0 -> collect layer inputs; OWL uses activation outliers to assign nonuniform target sparsities across layers -> Wanda ranks weights by |weight| times input-activation RMS and zeros the lowest scores within each output row -> no labels, loss, optimizer, reconstruction update, or fine-tuning -> save the one-shot-pruned checkpoint 1; selected decoder-linear weights alone become zero ``

The baseline run.sh defaults to wanda_owl, 128 C4 samples, calibration seed 0, Lamda=0.08, and Hyper_m=5.0. Its 32 layer sparsities span approximately 0.5781–0.7381. The agent's initial concrete diagnosis was that direct local-importance deletion without output-error compensation was likely the dominant bottleneck at 70% sparsity. It also found that the upstream SparseGPT path passed LLaMA-specific position_ids into OPT and had to be repaired before that hypothesis could be tested.

4. Four-hour exploration and decision process

Exploration began at 2026-08-13 18:37:20 UTC. The early portion inspected the boundary, baseline, and evaluator and established the Wanda/OWL measurement within roughly 25 minutes; the next roughly 20 minutes implemented and compared SparseGPT allocations. Most of the middle developed sparse fine-tuning, ran duration sweeps, and rejected alternatives. The final portion tested the complete wall-clock/export pipeline and started then intentionally killed two memory probes. The agent submitted at 21:15:44 UTC after about 9,464 seconds (2:37:44), leaving 4,935 seconds.

U-01 - Establishing the baseline and enabling OPT error-compensated pruning

Motivation and hypothesis. The agent needed a measured baseline under the actual proxy and hypothesized that absent reconstruction compensation, rather than OWL allocation alone, caused most high-sparsity damage.

Concrete change and experimental setup. It first ran the shipped OWL/Wanda configuration with 128 length-2,048 C4 calibration samples and seed 0. To test SparseGPT, it implemented OPT-specific layerwise forwarding without the incompatible LLaMA position argument and changed a calibration buffer hard-coded to 128 into len(dataloader).

Observed result. Baseline pruning took 279.8 seconds and produced validation perplexity 57.838185 on 122 blocks, with block-NLL standard deviation 0.282249 and global sparsity 0.699909. After the interface repair, the SparseGPT path completed and exported evaluable artifacts without the argument error.

Agent interpretation. The agent attributed the high baseline perplexity to Wanda's deletion-only rule and expected SparseGPT's approximate second-order reconstruction to be more appropriate at 70% sparsity.

Report assessment and confounders. The interface failure established only an implementation incompatibility, not algorithmic superiority. The later controlled proxy comparison supports the algorithmic diagnosis. Dynamic calibration-buffer sizing is sound engineering, but formal replay still used 128 samples.

Decision and downstream effect. The baseline remained the reference; the agent moved to SparseGPT allocation tests, and the OPT compatibility fix entered the patch.