Recorded results
Case studies
Seven recorded runs on an unsloth/Llama-3.2-1B-Instruct fine-tune, each with a defect planted on purpose. Of the seven, 4 confirmed what they set out to test, 2 were partly confirmed, and 1 was inconclusive. The strongest single result is the counterfactual retrain: a capability fell from 0.94 to 0.44, Gradian attributed 75% of the negative influence to a planted cluster of 51 examples, and removing those examples returned the capability to 0.94 exactly.
The runs that did not work are published with the reason. Two of them fail in the same way, and it is a limitation worth knowing before you trust any attribution result: a log-likelihood proxy metric can rise under a defect that genuinely damages the model, because a fine-tune mostly teaches answer format. Where that happened, the audit still named the real cause and the influence scores were meaningless. Use an exact-match metric.
Experiment D, unsloth and HuggingFace backend parity, has no recorded pass and so has no page here. The contract-level tests pass on CPU; the end-to-end comparison has not been run on a GPU. GPU validation covers how to run the suite yourself.
- Experiment A and CConfirmed
Finding the 51 poisoned examples that broke a LoRA fine-tune
Capability 0.94 → 0.44 → 0.94. The accused cluster carried 75% of the negative influence.
- Experiment BConfirmed
Why 12 epochs over 800 examples broke a LoRA fine-tune
Regressed 6.08 nats, 16 of 16 items flipped. The audit named the epoch count, not the data.
- Experiment BConfirmed
Why an effective batch size of 1 broke a LoRA fine-tune
Regressed 2.43 nats. Four independent checks named the same cause from three different inputs.
- Experiment BConfirmed
Why a learning rate that is too high breaks a LoRA adapter
Regressed 1.84 nats. One critical finding, and it was the learning rate.
- Experiment BPartly confirmed
Why max_seq_length silently truncated every training completion
Two criticals, correctly identified. The attribution half was uninformative, and the report said so.
- Experiment BPartly confirmed
Does attention-only LoRA break a fine-tune? This run says no
The check fired and the data was exonerated — but the capability improved 3.31 nats, so there was nothing to attribute.
- Experiment AInconclusive
Why train/eval contamination invalidates a fine-tune diagnosis
100% train/eval contamination. Gradian refused to call it a diagnosis, and was right to.