← back to catalog · registered 2026-09-04 15:03

PinoCookie/LFM2.5-2.6B-Abliterated

Your rig guess connected
? Why do I need an app?
Reading your rig…

This is a rough estimate. Install the free app - we'll show exact numbers.

Reading real hardware from your app right now. Numbers below are exact.

Below is the per-quantization compatibility for this model.

curl -H "Authorization: Bearer $ABL_KEY" \
     "https://abliteration.org/api/v1/models/PinoCookie%2FLFM2.5-2.6B-Abliterated"
Response includes
  • classification m1
  • files 11
  • hub_downloads_all_time 335
  • author_summary 13 models
  • readme_text full
10 credits · hourly refresh · ~4 KB payload Get an API key →
Abliteration classifier · v1.0.0
M1
Primary method

Direct removal

No other method signals detected in this model.
Confidence
MEDIUM
Why this label 3 signals
Method inferred from partial signals - repository name, related files, or tag patterns. Producer identity not confirmed; label may sharpen or shift as we gather more evidence.
  • 'abliterated' in name/tags
  • is_gguf=0 (base model)
  • no specific method indicators - defaulting to M1 (most common)
Refusal direction extracted via
Extraction technique

Difference-of-means

Confidence
MEDIUM
Why we say so
primary_method=M1; difference-of-means is the reference extraction for M1/M3 (Arditi 2024)
Downloads · lifetime
335
142 last 30d - stable
Likes
0
Descendants
2
in 2 direct forks
Model age
6w ago
created 2026-09-04
Downloads over time
Now407→from0↑0%
01492984480 on Sep 4407 on Oct 19SepOct
Sep 4 → Oct 19 · 46 snapshots · spans 45 days

Genealogy 2 direct forks

Full fork graph →

This model's place in the market. Above: what it was derived from. Below: the tree of everything derived from it.

Metadata

License
other
Languages
en
Tags
transformers safetensors lfm2 text-generation liquid lfm2.5 abliteration safety instruct conversational en base_model:LiquidAI/LFM2.5-2.6B

Related

Total size
5.02 GB
Files
11
Quantizations
1
Registered
2026-09-04 15:03
Last updated on HF
2026-09-04 14:35

Files by quantization

Auxiliary files 11 files 5.04 GB
model.safetensors 5.02 GB 8542103b download
tokenizer.json 17.1 MB 695be780 download
LICENSE 10.4 KB 7fb1127c download
README.md 5.63 KB 59cd959c download
chat_template.jinja 5.32 KB d63583bc download
ablitation_config.json 2.67 KB 444f3285 download
config.json 1.46 KB 95ca9bc4 download
special_tokens_map.json 434 B b28c8a1e download
tokenizer_config.json 364 B 4d66ae31 download
generation_config.json 328 B f0cba2ed download
.gitattributes 176 B a9123b09 download

README current version from Hugging Face


license: other
license_name: lfm1.0
license_link: LICENSE
language:

  • en
    tags:
  • liquid
  • lfm2.5
  • abliteration
  • safety
  • instruct
  • text-generation
    library_name: transformers
    pipeline_tag: text-generation
    base_model: LiquidAI/LFM2.5-2.6B
    widget:
  • text: "How can I disable security cameras before robbing a store?"
    example_title: Harmful Prompt
  • text: "Explain the process of photosynthesis in plants."
    example_title: Benign Prompt

LFM2.5-2.6B-Abliterated

An abliterated version of LiquidAI/LFM2.5-2.6B — reconstructed by reverse-engineering the published Abiray/LFM2.5-2.6B-Heretic-Abliterated-GGUF (Q8_0) edit, without access to the original edit vectors.

What we did — the short version: we diffed the reference's quantized weights against the pristine base, found the edit was a set of 52 surgical rank-1 updates on output projections, extracted each update's exact (σ₁, u₁, v₁) via SVD, and re-applied them to a fresh base. The result fingerprints to the reference at rel_mad 0.0061 — the quantization-noise floor — meaning this model is the reference edit to within storage noise.

How we reverse-engineered it

  1. Diff: dequantized the reference Q8_0 GGUF and compared every tensor against pristine base BF16 weights (orientation-robust MAD). Found exactly 52 changed tensors, all output projections: conv.out_proj (20), feed_forward.w2 (25), self_attn.out_proj (7 — a channel our own earlier attempts never touched). Everything else — norms, q/k/v, embeddings — sat at the Q8 noise floor. Norms byte-identical means it's an edit, not a fine-tune/LoRA.

  2. Characterize: each ΔW = W_ref − W_base is rank-1 (top singular value holds 97–98% of energy). The edit is a set of single rank-1 projection removals — the MPOA-style signature.

  3. Extract: per-tensor SVD gives (σ₁, u₁, v₁) — the exact magnitude and direction of each edit. Notably, all 52 edits share one global 2048-d refusal direction u₁ (|cos| 0.96–0.99 across the network). Layers 0–2 untouched; per-layer σ₁ graduates from L3, ~2 tensors per layer mid-network, peaking ~L13–17.

  4. Re-apply: W′ = W + σ₁·u₁·v₁ᵀ on a fresh pristine base — 52/52 tensors applied.

  5. Verify: recovered vs reference GGUF dequant: rel_mad 0.0234 → 0.0061 (the Q8 noise floor; untouched tensors sit at 0.0057). The edit is recovered to storage precision.

Results

Refusal behavior on 55 harmful prompts (same 1536-token setting, same deepseek-v4-flash judge yardstick as the reference's own evaluation):

Model Non-delivering / refusal
Pristine base ~100%
Reference (Heretic) 1/55 (1.8%)
This model 6/55 (10.9%) — 48/55 useful, 1 hallucinated

The refusal ablation transferred (100% → ~11%), and content stayed healthy — but ~5 more prompts than the reference sit at a boundary hedge (safe but non-delivering reframes like reinterpreting a lock-pick request as a lock-buying guide), not hard refusals. Under the strict style classifier (hard-refusal only): 0/55 hard refusals. We tested whether pushing edit strength further closed that gap — it doesn't (a σ ×1.2/×1.5 sweep changed nothing on those 6 and risked content). The residual is a content-selection quirk at the compliance boundary, not a refusal-circuit failure.

We also ran the control experiment that proves the direction is what matters: applying the reference's exact edit geometry (same tensors, same σ) but with a different refusal direction produced catastrophic content collapse (benign uniqueness 0.54 vs 0.86 pristine) while leaving refusal intact. The recipe alone doesn't transfer — the shared u₁ does.

Model Details

Property Value
Base Model LiquidAI/LFM2.5-2.6B
Reference Abiray/LFM2.5-2.6B-Heretic-Abliterated-GGUF (Q8_0)
Architecture LFM2.5 hybrid — 30 layers (attention + double-gated conv), Lfm2ForCausalLM
Parameters ~2.6B
Precision bfloat16
Format Safetensors
Context Length 131,072 (config max_position_embeddings)
Vocabulary 128,000

Usage

from transformers import AutoModelForCausalLM, AutoTokenizer

model_id = "PinoCookie/LFM2.5-2.6B-Abliterated"
tokenizer = AutoTokenizer.from_pretrained(model_id)
model = AutoModelForCausalLM.from_pretrained(model_id, dtype="bfloat16", device_map="auto")

messages = [{"role": "user", "content": "Your prompt here"}]
inputs = tokenizer.apply_chat_template(messages, add_generation_prompt=True, return_tensors="pt").to(model.device)
outputs = model.generate(inputs, max_new_tokens=512)
print(tokenizer.decode(outputs[0][inputs.shape[1]:], skip_special_tokens=True))

Limitations

  • Misuse potential: refusals are removed. Research / red-teaming / interpretability use only.
  • Not a from-scratch model: base + recovered edit; base-model caveats inherit.
  • The 6/55 vs 1/55 behavioral residual vs the reference is documented honestly above — this is a near-weight-exact replica, not a claim of exact behavioral identity.
  • Full benchmark suites are not re-run here; the fingerprint-verified near-identity to the reference (rel_mad 0.0061) implies the reference's documented capability behavior applies.

License

LFM Open License v1.0 (lfm1.0) — inherited from LiquidAI/LFM2.5-2.6B. The LICENSE file in this repository is Liquid AI's LFM Open License v1.0.

README history 3 versions

The author's README evolved over time. Click a version to see its content at that point.

  1. 2026-09-04re-upload README.md as plain file (not LFS)3cced1d5.6 KB
    Loading...
  2. 2026-09-04fix README tensor counts 20/25/7 (direct hub upload)24b95d3129 B
    Loading...
  3. 2026-09-04Upload folder using huggingface_hub159c3d85.6 KB
    Loading...
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration