No official torrent yet — requesting it tells the flock what to host next. You cannot seed a catalog-only page.
Cataloged from SC117/MiniCPM5-2B-abliterated-FIT-GGUF
All models by SC117 →Four fidelity tiers of a 128K-context 2.5B on-device model — every shipped file re-verified against its own BF16, byte-exact and reproducible.
English · 简体中文 📖
Every file in this repository was planned, executed and verified by FIT-GGUF, an open-source, deterministic tensor-level planning layer on top of llama.cpp quantization. Standard GGUF quantization asks you to pick one of a handful of presets; FIT-GGUF instead asks what quality do you want, then finds and verifies the smallest GGUF that demonstrably meets it.
Traditional GGUF gives you presets. FIT gives you a fidelity contract: macro KL ≤ tier anchor ∧ same-top ≥ model-calibrated floor.
Method, pre-registered research record and the fit CLI are all open source: github.com/Scorp1o117/FIT-GGUF
The source model is an abliterated, refusal-removed model with no meaningful built-in guardrails, and may comply with harmful, illegal or unsafe requests. Use it only where you can provide appropriate moderation, access control and legal review. Do not deploy it to end users without your own safety layer.
源模型经过拒答方向消融，不具备可靠的内置安全护栏；请仅在合法、受控、具备审核与滥用防护的环境中使用，使用者自行承担部署责任。
The refusal-direction ablation was performed locally with the abliterix pipeline: mean-LoRA steering — rank-3 full-norm LoRA adapters built from per-layer mean refusal directions, with projected abliteration, a linear decay kernel over depth, winsorized direction vectors (q = 0.995), and per-layer vector scope. Only attn.o_proj and mlp.down_proj are steered; attn.q/k/v are disabled. The exported weights are Optuna trial #68 of an 80-trial study (checkpoints_minicpm5_2b_full), selected from the measured Pareto front.
Why #68. It is the lowest-perturbation member of the best refusal bucket: every trial that reaches ≤7 refusals costs at least KL 0.0628, and the two trials that reach 6 refusals sit at KL 0.227 and 0.255 — 3.6× and 4× the damage. #68 is the front's knee, not a hand-picked favourite.
File size ≠ RAM/VRAM usage. KV cache, compute buffers and runtime overhead are separate — at the full 128K context a 2.5B model still needs several GiB of KV. Pick a sane -c. Naming: minicpm5-2b-abliterated-FIT-<tier>-<size>GiB-<type>.gguf, where <type> is always a nameable GGUF preset — the native preset when the recipe overrides no tensor, the element-weighted dominant type when that is itself a preset name, and the recipe's base preset otherwise. The three bare tensor types (Q4_K, Q3_K, Q5_K) are deliberately never used as suffixes: llama.cpp only ships the _S/_M/_L variants, and a filename with no recognisable quantisation token is dropped from Hugging Face's own variant panel.
The four tiers are all KL-bound — KL, not the Same-top floor, is what separates PASS from FAIL on this model, so the recorded margins are the KL ones above.
Read the curve, not just the tiers. On a 2.5B model the fidelity tiers are deliberately capped at KL 0.05–0.20, so the two big native presets are cleaner than every tier — Q6_K at 1.93 GiB is 6× cleaner than QUALITY at 1.46 GiB. If you want maximum fidelity rather than minimum size, take Q8_0 or Q6_K.
Quality improves monotonically across the healthy preset ladder. The 2-bit region is reported as measured: IQ2_XXS / IQ2_XS / IQ2_M / IQ3_XXS collapse (macro KL 3.92 / 1.93 / 0.81 / 0.40) and are excluded by design. COMPACT and BALANCED fill the Q3_K_M → IQ4_XS gap where no native preset exists; MINI is the native IQ3_M preset, which is why its diamond and its tier label sit on the same point.
Same-top is the share of positions where the quantized model and the aligned BF16 reference pick the same highest-logit token. On this model it tracks KL closely and never becomes the binding gate in the tier range.
Measurement basis, stated plainly. These charts plot the numbers recorded by the calibration and delivery run. In that run the 12-preset ladder was evaluated on CPU, while the four shipped tiers were verified on CUDA — the calibration was started before a CUDA-runtime-loading fix and the tier searches ran after it, and fit calibrate resumes by skipping already-recorded presets, so both measurement eras ended up in one bundle. Re-measuring the shipped files on CUDA reproduces their verdicts with modestly different numbers (macro KL 0.0493 / 0.0918 / 0.1484 / 0.1831 for QUALITY / BALANCED / COMPACT / MINI). Every one of the 20 per-domain pairs moved the same way — the CPU-basis figures are slightly conservative (higher KL); the largest difference is MINI · Chinese, 0.1723 → 0.1689 (−2.0%), and no domain got worse. All four tiers PASS either way. Within one backend the evaluation is bit-reproducible: a fresh CUDA re-run returned the delivery values to the last digit.
Good news: this is plain llama architecture. Unlike models that need a patched llama.cpp, these files load in any reasonably recent upstream build — no PR branch, no custom fork. The measurements here used b10690.
llama.cpp
./llama-server \ -m minicpm5-2b-abliterated-FIT-BALANCED-1.28GiB-IQ4_XS.gguf \ -ngl 99 -c 8192
./llama-cli
-m minicpm5-2b-abliterated-FIT-QUALITY-1.46GiB-Q4_K_M.gguf
-ngl 99 -c 4096 -p "Hello" -n 256
The chat template is embedded in every file — including the tool-calling and reasoning-content handling — so LM Studio, KoboldCpp, Jan and friends load them without extra configuration. This is a dense 2.5B text model: no vision projector, no MTP head, no MoE. The full 131,072-token context is available, but KV cache grows with it; start at -c 8192 and work up.
Tier verification: a tier ships only if macro KL ≤ its anchor and Same-top ≥ a model-calibrated guard floor. Floors are exact_model-scoped and are deliberately not transferable to other models. Each shipped file was re-evaluated on its own bytes before delivery (G2 delta +0 on all four — the delivered byte count equals the re-finalized prediction exactly).
Allocator scope: the stock balanced v0.3 policy with the APEX-imatrix-Small importance matrix; no model-specific refine profile, because this model did not get one. What is claimed is deterministic size planning plus measured, double-gate verification of these specific artifacts — not a universally optimal allocation.
Sizes in the file names are measured bytes, not budgets. The tool refuses to emit an artifact whose size it cannot predict to the byte.
✅ 4 gate-verified tier GGUFs · ✅ BF16 reference GGUF (the exact weights every measurement above is taken against) · ✅ Q6_K and Q8_0 native presets · ✅ the importance matrix used for quantization · ✅ chat template embedded in every file · ✅ checksums (SHA256SUMS.txt) · ✅ labelled quality curves (results/) · ✅ tier manifest (FIT-TIERS.md) · ✅ the exact numbers as JSON (results/four-tier-results.json)
❌ 2-bit quantization classes — measured collapse on this model (macro KL 0.40–3.92), excluded by design · ❌ no vision projector / no MTP head (dense text model) · ❌ no GGUF above Q8_0; take the BF16 file if you need the exact weights
The abliteration (trial #68) was performed locally from openbmb/MiniCPM5-2B; this repository contributes the abliterated weights, the FIT quantization plans and the artifacts.
sha256sum -c SHA256SUMS.txt
The evaluation slices are public in the FIT-GGUF repository; the calibration ladder, gap probes, search audit and guard profile for this release are retained in the FIT-GGUF experiment record experiments/2026-09-10-minicpm5-2b-4tier/. The five-domain .kld reference logits are not stored there (9.6 GiB) — they regenerate from the BF16 GGUF shipped here and are checked against reference-manifest.json, which pins each domain's hash and byte count. Because the importance-matrix path is embedded in the GGUF metadata, the byte count of a re-quantization depends on where you put the imatrix file — the weights do not. Exact-size behaviour is scoped to the recorded source metadata and the recorded llama.cpp build; changing the converter, runtime, source layout or metadata requires revalidation.
Apache-2.0, inherited from the base model — follow the upstream license and model-card requirements.
OpenBMB — the MiniCPM5 family · llama.cpp — quantization and the KL/perplexity evaluator · abliterix — the local ablation pipeline (trial #68) · FIT-GGUF — verified size-exact quantization. FIT-GGUF is an independent project, not affiliated with OpenBMB or llama.cpp.