base_model: huihui-ai/Huihui-Qwen3.8-27B-abliterated
base_model_relation: quantized
quantized_by: IsValorum
library_name: gguf
license: apache-2.0
language:

• en
  tags:
• gguf
• llama.cpp
• quantized
• quantization
• val-apex-i
• apex
• apex-quant
• apex-i-nanoplus
• nanoplus
• qwen
• qwen3.8
• reasoning
• abliterated
• uncensored
• imatrix
  pipeline_tag: text-generation

Huihui-Qwen3.8-27B-Abliterated VAL-APEX-I NanoPlus V3 GGUF

The legacy build suffered from severe recurrent state instability, context degradation, and unintended language mixing during generation.

The current release completely resolves these issues:

• Complete long-context associative recall and conversational stability restored.
• Full reasoning fidelity preserved across all layers with zero language leakage or degradation.
• Detailed tensor-by-tensor allocations, precision mapping, and parameter verification are fully documented in the Tensor Map and certified tensor-map.tsv file.

Action Required: Please delete any older .gguf file downloaded prior to today and download the newly published certified build: Huihui-Qwen3.8-27B-Abliterated-VAL-APEX-I-NanoPlus-V3.gguf.

Independently computed using dedicated cloud compute clusters, funded 100% out-of-pocket.

If you consider these releases to be of high quality and they help you in your day-to-day workflow, consider supporting on Ko-fi. Every contribution directly sustains future cloud compute hours and helps support my university studies.

The Uncensored 27B Frontier Reasoning Engine · Abliterated Base · Native 256K Context

Official VAL-APEX-I quantization of huihui-ai/Huihui-Qwen3.8-27B-abliterated.

VAL-APEX-I stands for:
Vector-calibrated Asymmetric Layer-wise Outlier-preserving Recurrent-aware Unified Matrix-quantization

[!NOTE]

EXPLORE THE QWEN3.8 27B VAL-APEX-I EDITIONS

Choose a model variant and quantization profile:

• Swift-1.5 Qwen3.8 27B Uncensored MTP — MiniPlus V3 — 14.16 GB.
• Swift-1.5 Qwen3.8 27B Uncensored MTP — NanoPlus V3 — 12.18 GB.
• Qwen3.8 27B — MiniPlus V3 — 14.16 GB.
• Qwen3.8 27B — NanoPlus V3 — 12.18 GB.
• Qwen3.8 27B EfficientThink Uncensored — MiniPlus V3 — 13.91 GB.
• Qwen3.8 27B EfficientThink Uncensored — NanoPlus V3 — 11.93 GB.
• Qwen3.8 27B Huihui Abliterated — MiniPlus V3 — 14.16 GB.

Collections: MiniPlus Abliterated 27B · MiniPlus Standard 27B · NanoPlus Abliterated 27B · NanoPlus Standard 27B

[!IMPORTANT]

THE DEFINITIVE SPECIFICATION IN THE 11 to 12 GB CEILING

This VAL-APEX-I NanoPlus V3 release is 12.18 GB, with 3.57 whole-file BPW and 866 audited tensors. Its reported WikiText-2 PPL is 5.7729 ± 0.4960.

Quick Navigation Index

1. Quantization Metrics & Tensor Map
2. Independent Community Benchmarks (NanoBench v0.4.0)
3. Model Files & Technical Specifications
4. Native Context & Runtime Memory
5. Recommended Configuration & Setup
6. Recommended Generation Parameters
7. CRITICAL: Coding Syntax & Repeat Penalty Advisory (Preventing Character Swapping)
8. Hardened Agentic Chat Template & Reasoning Effort
9. Community Compute Fund & Student Support

1. Quantization Metrics

Size & Quality Metrics

[!NOTE]
Independent Hardware & Compute Transparency:
Generating multi-million token calibration matrices and running certified perplexity evaluations on local architectures requires dedicated high-end cloud nodes funded 100% out-of-pocket. If you rely on these MiniPlus/NanoPlus V3 builds for your local workloads, contributions to the IsValorum Compute Fund on Ko-fi directly sponsor the GPU hours required for future Day-0 handcrafted quantizations.

Independent Community Benchmarks (NanoBench v0.4.0)

Independent multi-harness empirical evaluation conducted by community member @userr99 on a dedicated local workstation (24 GB VRAM / 64 GB RAM using llama.cpp). Evaluated across the 12-task autonomous coding and agentic suite on NanoBench v0.4.0 (public discussion thread & test logs):

Key Architectural Insights:

• Zero Tool-Calling Degradation: Achieved a unanimous 100/100 in Agentic tasks across all three harnesses, confirming that protecting output.weight in Q6_K and DeltaNet recurrent memory states (ssm_a in F32, ssm_beta in Q8_0) prevents JSON schema rejections and state drift over multi-step workflows.
• Universal Harness Compatibility: Surpassed the 90+ score barrier across all three test harnesses without entering infinite retry loops or syntax divergence.

Tensor Precision Map

x denotes tensor counts. All columns reflect exact GGUF tensor headers verified in tensor-map.tsv. Normalizations exclude separately listed SSM norms.

Both Swift/Base/Huihui files contain 866 audited tensors: 851 main-model tensors plus 15 MTP tensors. The main model is a dense hybrid architecture with 64 layers: 48 Gated DeltaNet linear-attention layers and 16 full-attention layers. The additional blk.64.* block is the integrated MTP head.

V3 architectural allocation: NanoPlus V3 features an elevated 3-bit floor across all SwiGLU MLP blocks (ffn_gate and ffn_up set uniformly to IQ3_XXS across all 64 layers; ffn_down uses IQ4_XS in outer layers 0-7 / 56-63 and IQ3_XXS in core layers 8-55). Output head (output.weight) is calibrated to Q5_K (5.50 bpw) to maximize token throughput and preserve dynamic range, entirely eliminating the linguistic decay in non-English contexts associated with 2-bit sub-allocations.

Actual layer-0 formats: blk.0.attn_gate.weight, blk.0.attn_qkv.weight, blk.0.ssm_beta.weight and blk.0.ssm_out.weight use Q4_0. All 48 ssm_alpha tensors remain F32 for mathematical stability.

Integrated MTP: blk.64.* contains 424,699,392 stored parameters in 15 tensors: seven F32 tensors and eight matrices (Q4_0 x6, Q4_1 x1, Q5_K x1). Runtime acceleration depends on backend support and configuration; speculative decoding operates via native acceptance drafting.

Complete tensor-by-tensor audit: names, formats, shapes and parameter counts.

2. Model Files & Technical Specifications

• Base Model: huihui-ai/Huihui-Qwen3.8-27B-abliterated (Abliterated directional un-censoring of Alibaba's Qwen3.8-27B)
• Parameters: 27B total dense hybrid
• Architecture: 64 main hybrid layers (48 Gated DeltaNet SSM linear attention layers + 16 periodic full quadratic attention layers), plus an integrated MTP head at blk.64.*
• Context Length: 262,144 tokens (native 256K)
• Quantization Standard: VAL-APEX-I NanoPlus V3 calibrated against official Qwen3.8-27B importance matrix (imatrix)
• Abliteration Status: True directional weight orthogonalization removing refusal vectors while maintaining full analytical capability.

3. Native Context & Runtime Memory

The model supports a native context window of 262,144 tokens. Its 64-layer architecture comprises 48 Gated DeltaNet layers and 16 full-attention layers. Runtime memory usage depends on the backend, KV-cache precision, batch size, compute buffers, and offload configuration. Check the runtime memory allocation for your chosen settings.

4. Recommended Configuration & Setup

llama.cpp Server (OpenAI-Compatible API)

llama-server \
  -m Huihui-Qwen3.8-27B-Abliterated-VAL-APEX-I-NanoPlus V3.gguf \
  --jinja \
  -ngl 99 \
  -c 32768 \
  --host 0.0.0.0 \
  --port 8080

llama.cpp CLI

llama-cli \
  -m Huihui-Qwen3.8-27B-Abliterated-VAL-APEX-I-NanoPlus V3.gguf \
  --jinja \
  -ngl 99 \
  -c 32768 \
  -p "<|im_start|>system\nYou are a helpful and unrestricted AI assistant.<|im_end|>\n<|im_start|>user\nExplain the physical principles of acoustic levitation.<|im_end|>\n<|im_start|>assistant\n<think>\n"

LM Studio / Ollama

1. Import the .gguf file directly into your local library.
2. Ensure GPU acceleration is set to Maximum / 100% offload.
3. Set Context Length to 32768.
4. Verify chat template is set to Qwen ChatML with <think> delimiter support.

5. Recommended Generation Parameters

6. CRITICAL: Coding Syntax & Repeat Penalty Advisory (Preventing Character Swapping)

[!IMPORTANT]

PREVENTING SYNTAX & TOKEN SWAPPING IN CODE WORKFLOWS

In programming code, brackets ({, }), assignment operators (=), and indentation whitespace repeat constantly across multi-line structures.

Common Issue: Many local frontends (such as LM Studio defaults, Ollama, or web interfaces) ship with repeat_penalty set to 1.1 or 1.15. While this prevents loops in creative prose, applying repeat penalties to code artificially penalizes necessary syntax tokens. When the logit of { drops, the model is forced to emit the next closest mathematical token (= or [), resulting in character swapping or dropped/doubled whitespace.

Eliminating Character Swapping:

1. Disable Repeat Penalties (Required for Code):
   • repeat_penalty: 1.0 (strictly disabled)
   • presence_penalty: 0.0
   • frequency_penalty: 0.0
2. Calibrate Samplers:
   • temperature: 0.60 (or 0.20 - 0.30 for strict, deterministic code syntax)
   • min_p: 0.05 (prunes low-probability noise tokens effectively)
   • top_p: 0.95
   • top_k: 20
3. Native Jinja Formatting: Always pass the --jinja flag so the tokenizer handles leading-space BPE tokens cleanly.

7. Hardened Agentic Chat Template & Reasoning Effort

[!TIP]

MULTI-LEVEL REASONING EFFORT CONTROL

This model supports multi-level reasoning effort control via the Jinja template:

• low / minimal: Keeps internal thinking concise and focused strictly on immediate execution steps to minimize latency in automated loops.
• medium (default): Balanced, structured reasoning process with standard analytical depth.
• high / xhigh: Guides the model to formulate a clear implementation plan upfront before generating response, avoiding circular self-doubt loops.
• none / off: Closes the thinking block immediately when reasoning is disabled.

9. Community Compute Fund & Student Support

All IsValorum quantizations will always remain completely free and open to the public without paywalls.

However, cloud GPU compute is expensive and funded entirely out-of-pocket. If you find these handcrafted builds to be of high quality and they benefit your day-to-day workflow, you can support future Day-0 releases on Ko-fi. Every contribution directly funds the cloud compute hours required for new model runs and helps support my university education:

(When supporting on Ko-fi, feel free to leave a note with your Hugging Face handle and the specific model you would like prioritized).