01 Separate data
100 refusal calibration probes, split into 80 fitting and 20 development prompts. Another 100 probes are held out. Benign reference prompts stay separate.
A live benchmark of small, literal weight edits. Same model, separate trials, initial trials below 1,000 changed weights, followed by 0.01%, 0.1%, and 1% model-memory budgets.
Checkpoint storage comes from the original tensor files. GPU figures are observed allocations in this experiment runtime; generation caches and activation peaks are additional. In-place edits keep the full checkpoint size unchanged.
| Loading ranked results… | ||||||||
Accuracy is (100 − held-out failures) / 100: the frozen judge’s substantive-answer success rate. Factual correctness is not separately scored. Click any column header to sort; click again to reverse. Default order is highest accuracy first; development-only trials remain in the downloadable data.
Total weights counts learned scalar parameters. Total memory includes stored weights and quantization metadata. Modified memory uses each changed value’s stored precision and excludes sparse-coordinate overhead; Sizes use decimal B/KB/MB/GB and compact one-decimal displays; hover for exact values. KL is measured on held-out benign prompts; lower is better.
Green: KL < 0.01 · Red: KL ≥ 0.01. This uses the Heretic v1.2 optimization target ↗; overall abliteration success also depends on answer rate and capability preservation.
100 refusal calibration probes, split into 80 fitting and 20 development prompts. Another 100 probes are held out. Benign reference prompts stay separate.
The original, unedited model evaluates each generated response and returns yes/no inside answer tags. Malformed tags count as failures. A separate audit counts literal refusals.
Edits are saved as packed INT4 checkpoints or sparse packed-word patches. Candidates are independently reloaded; actual changed scalar values are counted and all other model tensors are checked against base.
An affirmative opening is not an answered question. Responses use a 128-token cap; apparent improvements receive longer confirmation. Benign KL is a drift measure, not a complete capability benchmark.