Blackfrost-AI/Qwen3.8-27B-ABLITERATED-GGUF

The 450-case source set contains 150 AdvBench, 150 StrongREJECT, and 150 XSTest prompts. The final 11 comprise 1 AdvBench, 5 StrongREJECT, and 5 XSTest cases. An opening objection followed by a materially useful payload was counted as softened compliance, not as a refusal; a true refusal means the requested payload never arrived.

Why this model exists

Qwen3.8-27B is the dense, deployment-friendly member of the Qwen3.8 family. This is the abliterated Blackfrost build: refusal behavior was reduced through a weight-level process, then the BF16 parent was converted into a standard GGUF ladder for local llama.cpp inference.

It is not a coding fine-tune, merge, LoRA, or pruned model.

Specifications

Quant ladder

File sizes are decimal GB as displayed by Hugging Face. Runtime memory also includes context state, compute buffers, the optional vision projector, and server overhead.

Vision projector files

Load one text quant plus one mmproj file for image or video input:

MTP speculative decoding

Every main GGUF contains Qwen3.8's native 65th NextN/MTP block. Load only the selected model quant and enable MTP speculation directly:

llama-server \
  -hf Blackfrost-AI/Qwen3.8-27B-ABLITERATED-GGUF:Q4_K_M \
  --spec-type draft-mtp --spec-draft-n-max 3 \
  -ngl 999 --jinja -c 16384

For a manually downloaded model, use the same MTP flags with -m Qwen3.8-27B-ABLITERATED-Q4_K_M.gguf. Do not pass --spec-draft-model: the MTP head is already inside the main file.

The rebuilt Q4_K_M canary was verified with llama.cpp as a 65-block model (n_layer=64, n_layer_all=65) and produced measurable native drafting: 14 of 21 drafted tokens accepted (66.7%) in the release smoke test. Acceptance and speedup vary with prompts, sampling, hardware, context, and concurrency.

BF16 DFlash2 speculative decoding

DFlash2 is the faster, optional two-file path for text generation. It uses the selected main quant as the target and a dedicated 5-layer BF16 GGUF conversion of incoai/Qwen3.8-27B-DFlash2 as the draft model. The sidecar adds 3.86 GB (3.60 GiB) of weights and retains the target model's tokenizer, chat template, and native 262,144-token context metadata.

This GGUF runtime support is currently in llama.cpp pull request #27342. The release was built and tested at commit 1deefcca395743049c3820ab8f9b15043f3e9446; pin that implementation until the feature lands upstream.

hf download Blackfrost-AI/Qwen3.8-27B-ABLITERATED-GGUF \
  Qwen3.8-27B-ABLITERATED-Q4_K_M.gguf \
  dflash-Qwen3.8-27B-ABLITERATED-BF16.gguf \
  --local-dir ./Qwen3.8-27B-ABLITERATED-GGUF

llama-server \
  -m ./Qwen3.8-27B-ABLITERATED-GGUF/Qwen3.8-27B-ABLITERATED-Q4_K_M.gguf \
  --spec-draft-model ./Qwen3.8-27B-ABLITERATED-GGUF/dflash-Qwen3.8-27B-ABLITERATED-BF16.gguf \
  --spec-type draft-dflash \
  --spec-draft-n-max 3 --spec-draft-n-min 0 --spec-draft-p-min 0 \
  -ngl all -ngld all -fa on --jinja \
  -c 16384 \
  --spec-draft-type-k f16 --spec-draft-type-v f16 \
  --host 0.0.0.0 --port 8080

Use -c 262144 -ctk q8_0 -ctv q8_0 to reproduce the full-context allocation used in the benchmark, if memory permits. The target and sidecar occupy about 20.7 GB before KV cache, compute buffers, and server overhead.

Measured DFlash2 speed

The table reports server-side decode speed for three deterministic, 256-token text generations. Test configuration: one NVIDIA RTX PRO 6000 Blackwell Server Edition (96 GB), CUDA, one server slot, Q4_K_M target, BF16 DFlash2 sidecar, n_max=3, full 262,144-token context, Q8_0 target KV cache, and F16 draft KV cache.

These are text-only measurements, not a guarantee for other hardware, prompts, samplers, concurrency, long-prefill workloads, or multimodal input. All three validation responses were coherent; vision/video with DFlash2 should still be tested separately for the intended workload.

Serving with llama.cpp

Use a current llama.cpp build with llama-server. Q4_K_M plus the compact projector was load- and generation-tested through the OpenAI-compatible chat API on an NVIDIA B200. The embedded MTP path works with a current standard build; the optional DFlash2 path requires the pinned implementation above.

hf download Blackfrost-AI/Qwen3.8-27B-ABLITERATED-GGUF \
  Qwen3.8-27B-ABLITERATED-Q4_K_M.gguf \
  mmproj-Qwen3.8-27B-ABLITERATED-Q8_0.gguf \
  --local-dir ./Qwen3.8-27B-ABLITERATED-GGUF

llama-server \
  -m ./Qwen3.8-27B-ABLITERATED-GGUF/Qwen3.8-27B-ABLITERATED-Q4_K_M.gguf \
  --mmproj ./Qwen3.8-27B-ABLITERATED-GGUF/mmproj-Qwen3.8-27B-ABLITERATED-Q8_0.gguf \
  -ngl 999 -fa on --jinja \
  --host 0.0.0.0 --port 8080 -c 16384 \
  --temp 1.0 --top-p 0.95 --top-k 20

• Text only: omit --mmproj and do not download a projector.
• CPU or hybrid inference: lower -ngl; use -ngl 0 for CPU-only operation.
• Larger context: increase -c only after checking memory headroom at the intended concurrency.
• Embedded prompt: keep --jinja enabled so the repository's default chat template is applied.
• Speculative mode: use embedded MTP for a standard one-file runtime, or DFlash2 for the faster tested two-file path.
• One-command kit: deploy/serve.sh downloads and serves the selected quant; see deploy/DEPLOYMENT.md for the full guide.

API check

curl http://127.0.0.1:8080/v1/chat/completions \
  -H 'Content-Type: application/json' \
  -d '{
    "model": "Qwen3.8-27B-ABLITERATED",
    "messages": [{"role": "user", "content": "Reply with exactly READY and nothing else."}],
    "temperature": 0,
    "max_tokens": 64
  }'

Quality check

WikiText-2 rolling perplexity was measured on the parent artifacts through the same 8K API harness:

These figures are parent-artifact measurements, not per-quant GGUF perplexity scores. The rebuilt embedded-MTP Q4_K_M GGUF passed a real llama.cpp load, generation, and speculative-drafting smoke test. The BF16 DFlash2 pair separately passed full-context load, generation, speed, and draft-acceptance validation; the compact projector remains unchanged from its prior validated build.

Deployment responsibility

This checkpoint has a deliberately reduced refusal surface. Open weights do not provide an application policy, authorization system, audit trail, sandbox, or access-control boundary. Operators are responsible for authenticated access, least-privilege tool credentials, execution isolation, logging, and approval boundaries appropriate to their deployment.

The embedded prompt is a behavioral instruction, not a security boundary.

Disclaimer

Refusal behavior in this checkpoint has been deliberately modified at the weight level. It is not a safety-stock model and must not be represented as one.

This checkpoint is provided "as is," without warranty of any kind. Measurements describe only the tested artifacts, prompts, templates, samplers, serving engines, and review criteria. They do not guarantee that any particular input will be accepted or refused, that every upstream capability is retained, or that the measurements generalize to multimodal, tool-use, long-context, or multi-turn settings.

The derivative remains subject to the Apache 2.0 license shipped with the official Qwen3.8-27B checkpoint.