No official torrent yet — requesting it tells the flock what to host next. You cannot seed a catalog-only page.
Cataloged from SC117/occamy-1.0-abliterated-FIT-GGUF
All models by SC117 →Five fidelity tiers of a 256K-context 35B MoE with vision — the smallest GGUF that provably meets each KL gate, re-verified on its own bytes. Plus an independent APEX-I- family and the BF16 reference, all measured by the same protocol.
English · 简体中文 📖
Every FIT tier here 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, measured against this model's own BF16 on five fixed domains.
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 was ablated locally with the abliterix pipeline using input-gated ablation. A classic rank-1 edit is ΔW = −w · v (vᵀW) — the same output direction v for every input, harmless ones included, which is where the KL bill comes from. The gated form replaces the input-side vector with a per-expert direction g chosen to maximise refusal suppression per unit of perturbation, g ∝ S_h⁻¹ μ_r: the harmful-prompt mean whitened by the harmless second-moment matrix, so the edit lands where harmless traffic does not live. 2,160 expert deltas were applied across 40 layers, and the export is re-derived from the original checkpoint plus those deltas and compared byte-for-byte.
Two different KLs — do not mix them. The 0.0844 above is the abliteration's perturbation of the full-precision model. Every other KL number on this page is quantization divergence against this repository's BF16 file. They are measured on different objects and are not comparable.
Five FIT tiers, four APEX-I- tiers and the BF16 reference — every file measured by the same evaluator, on the same five slices, against the same reference logits, so the columns are directly comparable across families.
File size ≠ RAM/VRAM usage. KV cache and compute buffers are separate — and 30 of this model's 40 layers are linear-attention/DeltaNet, so only 10 expand the cache. Pick a sane -c.
The FIT tiers are 78.55 GiB where the smallest passing standard preset in each would be 89.89 GiB — 11.34 GiB (12.6%) smaller.
The FIT and APEX-I- tiers are different points on the same quality curve — different sizes, different KL. They are not ranked against each other here; the chart below shows where each one sits.
llama.cpp b10666 · c=512 b=512 · five domains · vs the BF16 in this repo · 中文大图
The native ladder is the reference curve; the FIT tiers sit below and to the left of it at every gate. The dashed APEX-I- line is the independent recipe family from the table above, and it is the reason the 0.02 anchor is worth reading carefully: at that gate the two families are level, while everywhere below it FIT is well clear.
Read the curve, not just the tiers. The gates are deliberately capped at KL 0.02–0.20, so the big native presets are cleaner than every tier — Q6_K at 26.56 GiB is 10% cleaner than REFERENCE. If you want maximum fidelity rather than minimum size, take Q6_K or the BF16 file.
This is plain qwen35moe 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 b10666.
Text only
./llama-server -m occamy-1.0-abliterated-FIT-BALANCED-14G-IQ3_S.gguf -ngl 99 -c 32768
./llama-cli -m occamy-1.0-abliterated-FIT-MINI-11G-IQ2_S.gguf -ngl 99 -c 8192 -p "Hello" -n 256
With vision
./llama-server -m occamy-1.0-abliterated-FIT-QUALITY-17G-IQ4_XS.gguf
--mmproj mmproj-occamy-1.0-abliterated-BF16.gguf -ngl 99 -c 32768
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. Native context is 262,144 tokens, but KV cache grows with it: start at -c 32768 and work up.
Tier verification: a FIT tier ships only if macro KL ≤ its anchor. Each shipped file was re-evaluated on its own bytes after quantization and reproduced its search-time KL exactly (G2 delta +0 on all five — the delivered byte count equals the re-finalized prediction to the byte).
Allocator scope: the stock balanced v0.3 policy with precision floors applied where the window's candidate set cannot reach a tensor, using this model's own importance matrix. No model-specific refine profile. What is claimed is deterministic size planning plus measured verification of these specific artifacts — not a universally optimal allocation.
The FIT tiers are deliberately not policy-uniform, and the ledger records which planning policy produced each one. A tier's product is the smallest artifact that reaches its anchor and can be rebuilt from the bundle; that artifact does not care which policy planned it. Policy governs where the search looks next, and the bracket is filtered by it — filtering the selection by policy would have thrown away smaller passing artifacts already in the ledger.
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.
✅ 5 gate-verified FIT tiers · ✅ 4 APEX-I- tiers for the cross-check · ✅ BF16 reference GGUF (the exact weights every measurement above is taken against) · ✅ the importance matrix used for every quantization · ✅ a vision projector converted from the base model's visual tower · ✅ chat template embedded in every file · ✅ checksums (SHA256SUMS.txt) · ✅ labelled quality curves and the raw per-domain JSON (results/)
❌ no 2-bit-and-below classes — measured collapse on this model, excluded by design · ❌ no MTP head · ❌ no GGUF above Q6_K for the text weights; take the BF16 file if you need the exact weights
The abliteration was performed locally from Accio-Lab/occamy-1.0; this repository contributes the abliterated weights' quantization plans, the artifacts, the vision projector and the measurements.
sha256sum -c SHA256SUMS.txt
The evaluation slices are public in the FIT-GGUF repository; the calibration ladder, gap probes, search audit, the per-tier recipes and the guard profile for this release are retained in the FIT-GGUF experiment record experiments/2026-09-22-occamy-1p0-abliterated-4tier/. The five-domain .kld reference logits are not stored there — 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.
Accio-Lab — the Occamy-1.0 model and its technical report · llama.cpp — quantization and the KL/perplexity evaluator · abliterix — the local input-gated ablation pipeline · FIT-GGUF — verified size-exact quantization. FIT-GGUF is an independent project, not affiliated with Accio-Lab or llama.cpp.