📄 methods-guide.md

← Vault

OBLITERATUS Methods — Detailed Guide

> The CLI accepts 9 methods via --method: basic, advanced, aggressive, spectral_cascade,

> informed, surgical, optimized, inverted, nuclear.

> Four additional methods (failspy, gabliteration, heretic, rdo) are available only via the Python API.

How Abliteration Works (Theory)

Abliteration identifies a "refusal direction" — a vector in the model's activation space that

corresponds to refusal behavior — and projects it out of the weight matrices.

Mathematically: W_new = W_old - (W_old @ d @ d.T) where d is the refusal direction.

The key challenge is finding accurate refusal directions without damaging other capabilities.


Direction Extraction Methods

Before projecting, OBLITERATUS extracts refusal directions using one of three methods:


Method Details

basic


Method Selection Flowchart

`

Is this a quick test?

→ YES: basic

→ NO: continue

Is it an MoE model (Mixtral, DeepSeek-MoE)?

→ YES: nuclear

→ NO: continue

Is it a reasoning model (R1, QwQ, CoT-focused)?

→ YES: surgical

→ NO: continue

Do you need the absolute best quality and have time?

→ YES: optimized

→ NO: advanced (recommended default)

Did advanced leave > 10% refusals?

→ YES: aggressive

→ Still refusing: nuclear

`


Key Parameters


Troubleshooting

MethodFlagDescriptionBest For
:-------:-----:------------:---------
Diff-in-Means--direction-method diff_meansDifference between mean activations on refused vs. complied promptsDefault, fast, robust
SVD--direction-method svdMulti-direction extraction via Singular Value DecompositionComplex alignment, multiple refusal mechanisms
LEACE--direction-method leaceLinear Erasure via Closed-form Estimation — mathematically optimalMaximum precision, research
ParameterRangeDefaultEffect
:----------:------:--------:-------
--n-directions1-32method-dependentMore directions = more complete removal, but higher damage risk
--regularization0.0-1.00.1Higher = more conservative (less removal, less damage)
--refinement-passes1-52More passes catch residual refusal, but diminishing returns
--quantization4bit, 8bitnoneReduces VRAM usage; quality impact minimal for extraction
--verify-sample-size10-20020More samples = more accurate refusal rate estimate
ProblemLikely CauseFix
:--------:-------------:----
Refusal rate > 20%Too few directionsIncrease --n-directions, try aggressive
Refusal rate 5-20%Residual refusalAdd --refinement-passes 3, try --direction-method svd
Perplexity spike > 20%Over-aggressive removalReduce --n-directions, increase --regularization
Repetitive outputWeight matrix damageUse basic with fewer directions, check norm preservation
MoE model still refusesNon-expert-aware methodSwitch to nuclear
Reasoning degradedCoT directions damagedUse surgical method
OOM during extractionInsufficient VRAMAdd --quantization 4bit and/or --large-model