T-Search-APEX-I-MiniPlus-V2.1-GGUF

<a id="quick-navigation"></a>Quick Navigation Index

<a href="https://ko-fi.com/isvalorum"><img src="https://ko-fi.com/img/githubbutton_sm.svg" alt="Support on Ko-fi" height="38"></a>

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.

1. Optimization History & Transparency Notice
2. Empirical Benchmarks & Fidelity Verification
3. The Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Formats
4. Model Files & Technical Specifications
5. Bundled Q8_0 High-Precision Multimodal Vision Projector
6. Surgical Tensor-by-Tensor Quantization Breakdown
7. Hardware Throughput & Offload Benchmarks (RTX 30 / 40 / 50 & RAM Streaming)
8. The 24GB Miracle: Full 256K Context Runs In VRAM!
9. Recommended Configuration & Setup
10. 1. High-Throughput Server with Built-in MTP Speculative Decoding (llama-server)
11. 2. Direct CLI Inference / Agentic Retrieval Harness
12. Recommended Generation Parameters (t-tech Official)
13. Model Inherent Behavior vs. Quantization Fidelity Notice
14. CRITICAL: Coding Syntax & Repeat Penalty Advisory (Preventing Character Swapping)
15. Hardened Agentic Chat Template & Reasoning Effort
16. Optional Support

T-Search APEX-I-MiniPlus-V2.1 GGUF

The Definitive 35B Agentic Retrieval MoE · Multi-Round Search & Evidence Synthesis · Bundled Q8_0 Vision Projector · Full 256K Context on 24GB Workstations

Welcome to APEX-I-MiniPlus-V2.1 for t-tech/T-Search (the specialized 35B Mixture-of-Experts architecture developed by t-tech as an agentic retriever that plans, executes multi-round searches, and synthesizes verifiable evidence chains).

Standard automated community quantizations uniformly degrade sensitive routing matrices and expert feed-forwards down to 2-bit codebooks, corrupting retrieval planning trajectories, hallucinating query filters, and dropping critical visual tokens.

APEX-I-MiniPlus-V2.1 was engineered differently. This is a 100% custom, hand-crafted tensor-by-tensor quantization built with mathematical precision overrides, calibrated importance matrices (imatrix), and an included high-precision Q8_0 multimodal vision projector (mmproj). Whether executing deep research harnesses on an everyday laptop or orchestrating autonomous search agents across 256K context on a 24GB workstation, this release delivers unmatched evidence grounding, zero router drift, and blistering system RAM streaming throughput.

[!TIP]

SYSTEM RAM INFERENCE: FULL OR PARTIAL

This APEX-I-MiniPlus release is designed for full or partial system-RAM inference. Depending on the processor, memory bandwidth, and DDR4/DDR5 configuration, generation can range from 20 to 45 tok/s. With partial GPU offload, systems that cannot fit 128K or more context entirely in VRAM can place the remaining model and context load in system RAM, maintaining stable, responsive generation at longer context lengths.

---

[!IMPORTANT]

THE DEFINITIVE SPECIFICATION IN THE 13–14 GB CEILING

This APEX-I-MiniPlus-V2.1 release represents the absolute technological limit of sparse Mixture-of-Experts quantization within the 15–16 GB download envelope. Every single tensor of its 40 layers and 256 micro-experts has been mathematically audited to maximize reasoning precision, eliminate recurrence state drift, and prevent AVX2 CPU dequantization stalls.

[!TIP]

🏆 EMPIRICAL BENCHMARK & QUALITY COMPARISON

Quantization Specification	File Size (Disk)	Memory Footprint (RAM/VRAM)	Average BPW	WikiText-2 Perplexity	Quality Tier Equivalent
Unquantized BF16 Base	approx. 70.0 GB	approx. 65.2 GiB	16.00 BPW	approx. 5.62 (Reference)	Full precision baseline
APEX-I-MiniPlus V2.1 (CURRENT)	15.23 GB	14.18 GiB	3.43 BPW	5.6716 ± 0.12975 (approx. ΔPPL +0.0516 / +0.92%)	Q5_K_L tier (bordering Q6_K)

Routing: all recipe-designated gate_inp and gate_shexp tensors remain in uncompressed F32, preserving zero routing drift.

[!WARNING]

DO NOT CONFUSE APEX-I-MINIPLUS WITH GENERIC COMMUNITY APEX-I-MINI!

Regardless of release version, NEVER confuse handcrafted APEX-I-MiniPlus builds with generic community APEX-I-Mini releases:

• Generic Community APEX-I-Mini: Uniformly compresses all core MoE experts down to aggressive 2-bit IQ2_S (dropping below the critical quality floor), leaves the sensitive token output head unarmored at 3-bit Q3_K_M, and compresses attention projections down to Q3_K. In deep retrieval and reasoning agents, this triggers hallucinated search operators, broken syntax brackets, and high perplexity spikes.
• Handcrafted APEX-I-MiniPlus (All Editions by IsValorum): Every single MiniPlus release is a custom tensor-by-tensor architecture that preserves uncompressed F32 router gates, armors the token output head in high-precision Q6_K, safeguards attention gates in Q8_0, and keeps core reasoning experts at or above calibrated 3-bit (IQ3_XXS/IQ3_S).

---

<a id="toc-01"></a>

Optimization History & Transparency Notice

We maintain our previous releases publicly as a transparent engineering record of continuous optimization. Below is the exact evolutionary roadmap of our MiniPlus architectures:

---

[!IMPORTANT]

EXPLORE THE ESTABLISHED 35B MoE MINIPLUS LINEUP

These are complementary APEX-I-MiniPlus V2.1 releases, not alternate downloads of the same model. Each receives the same tensor-by-tensor approach, integrated MTP where supported, and a design suitable for full or partial system-RAM inference. Choose the model whose native strengths best fit the work you want to do:

• Qwen3.6-35B-A3B MTP APEX-I-MiniPlus-V2.1 — a versatile frontier MoE for broad reasoning, multilingual work, agents, tool use, and multimodal tasks.
  • Best for: General reasoning, agent workflows, tool calling, and flexible multimodal use.
• Qwen3.6-35B-A3B MTP APEX-I-MiniPlus-V2.1 Abliterated — the V2.1 refusal-ablated Qwen3.6 edition for users who deliberately prefer reduced refusal behavior.
  • Best for: Workflows where an abliterated Qwen3.6 variant is explicitly desired.
• Ornith 1.5 APEX-I-MiniPlus-V2.1 — a software-engineering-focused MoE designed for repository-scale coding and autonomous engineering agents.
  • Best for: Repository-scale development, multi-file code changes, and software-engineering agents.
• Tiel Coder APEX-I-MiniPlus-V2.1 — a specialist coding MoE tuned for agentic programming, iterative tool use, and implementation-heavy work.
  • Best for: Focused coding sessions, iterative debugging, and tool-driven implementation.

These remain distinct model families and editions with their own behavior and empirical results. Pick by workload and intended alignment behavior rather than treating them as interchangeable quantization variants.

---

<a id="empirical-benchmarks"></a> <a id="toc-02"></a>

Empirical Benchmarks & Fidelity Verification

The comparison table near the top consolidates the model-specific BF16 baseline, final GGUF PPL, delta, published main-file size, BPW, and fidelity tier. The routing treatment is preserved in the note directly beneath it.

<a id="quality-spectrum"></a> <a id="toc-03"></a>

🏆 The Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Formats

Where APEX-I-MiniPlus V2.1 sits in the landscape of local quantization formats:

---

<a id="model-files"></a> <a id="toc-04"></a>

📦 Model Files & Technical Specifications

---

<a id="vision-projector"></a> <a id="toc-05"></a>

👁️ Bundled Q8_0 High-Precision Multimodal Vision Projector

Standard community uploads often omit the multimodal projector or supply uncompressed FP16 files, bloating memory.

This release includes mmproj-Q8_0.gguf:

• Mathematical Precision: Quantized using calibrated Q8_0 with uncompressed F32 normalizations, preserving zero visual artifacting during document inspection, PDF table parsing, and OCR grounding.
• Seamless Deployment: Place mmproj-Q8_0.gguf alongside the main model file; llama.cpp and llama-server load it automatically via --mmproj mmproj-Q8_0.gguf.

---

<a id="tensor-breakdown"></a> <a id="toc-06"></a>

🛠️ Surgical Tensor-by-Tensor Quantization Breakdown

Every tensor has been verified directly from the compiled binary weights:

---

<a id="throughput-projections"></a> <a id="toc-07"></a>

⚡ Hardware Throughput & Offload Benchmarks (RTX 30 / 40 / 50 & RAM Streaming)

Empirically verified in Unsloth Studio & llama.cpp:

---

<a id="context-scaling"></a> <a id="toc-08"></a>

🌐 The 24GB Miracle: Full 256K Context Runs In VRAM!

T-Search APEX-I-MiniPlus-V2.1 fits the entire 256K context window within 24GB VRAM:

Note: Leaves comfortable headroom for display drivers and compute buffers on standard 24GB GPUs (RTX 3090, RTX 4090, RTX 5090).

---

<a id="recommended-setup"></a> <a id="toc-09"></a>

🚀 Recommended Configuration & Setup

<a id="toc-10"></a>

1. High-Throughput Server with Built-in MTP Speculative Decoding (llama-server)

T-Search.APEX-I-MiniPlus-V2.1.gguf includes integrated Multi-Token Prediction (MTP) draft layers. To enable ultra-fast self-speculative execution, pass --spec-type draft-mtp:

llama-server.exe \
  -m T-Search.APEX-I-MiniPlus-V2.1.gguf \
  --mmproj mmproj-Q8_0.gguf \
  --spec-type draft-mtp \
  --draft-max 2 \
  --port 8080 \
  --flash-attn on \
  --fit on \
  -c 32768 \
  --cache-type-k q8_0 \
  --cache-type-v q8_0

(Note: Keep --draft-max tight at 1 or 2 for optimal MTP acceptance depth on agentic retrieval trajectories. To run in standard single-stream mode without MTP, simply omit --spec-type draft-mtp).

<a id="toc-11"></a>

2. Direct CLI Inference / Agentic Retrieval Harness

llama-cli.exe \
  -m T-Search.APEX-I-MiniPlus-V2.1.gguf \
  --mmproj mmproj-Q8_0.gguf \
  --spec-type draft-mtp \
  --draft-max 2 \
  -c 32768 \
  -ngl 99 \
  --temp 0.60 --top-p 0.95 --top-k 20 \
  -p "<|im_start|>user\nPlan a multi-round retrieval strategy for verifying quantum error correction milestones.<|im_end|>\n<|im_start|>assistant\n"

---

<a id="generation-parameters"></a> <a id="toc-12"></a>

⚙️ Recommended Generation Parameters (t-tech Official)

Official generation guidelines specified by t-tech for agentic search retrieval:

---

<a id="quantization-fidelity"></a> <a id="toc-13"></a>

🔍 Model Inherent Behavior vs. Quantization Fidelity Notice

[!IMPORTANT] Any behavioral nuances, stylistic tendencies, domain-specific search habits, or zero-shot edge-case oversights stem entirely from the original unquantized checkpoint weights and fine-tuning distribution, NOT from the APEX-I quantization process. Handcrafted APEX-I-MiniPlus strictly preserves mathematical tensor fidelity—keeping 100% of expert routing matrices (gate_inp) in uncompressed F32 (zero router drift), armoring the token output head in Q6_K, and safeguarding attention gates in Q8_0. Empirical verification confirms near-zero perplexity loss (ΔPPL ≈ +0.05), ensuring that token logits, routing decisions, and reasoning trajectories are mathematically faithful to the original base model.

<a id="toc-coding-advisory"></a> <a id="coding-advisory"></a>

[!IMPORTANT]

CRITICAL ADVISORY FOR CODING WORKFLOWS: PREVENTING SYNTAX & TOKEN SWAPPING

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.

Verified Upstream Behavior: This self-correcting behavior (where the model notices the mistake in its thinking loop but repeats the substitution) is documented on official upstream base checkpoints and Q8 builds (Ornith Discussion #34 and Discussion #22). It is completely eliminated by proper sampling configuration:

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 ( { vs {, = vs =) cleanly.

<a id="toc-chat-template"></a> <a id="chat-template"></a>

[!TIP]

HARDENED AGENTIC CHAT TEMPLATE (JINJA)

An optimized chat_template.jinja is included at the root of this repository. It hardens agent workflows and multi-turn stability:

1. Native reasoning_effort Multi-Level Control:
   • 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 code, avoiding circular self-doubt loops.
   • none / off: Closes the thinking block immediately (<think>\n\n</think>) when reasoning is disabled.
2. Tool-Calling Safeguard (Anti-Premature Stop): Prevents the model from terminating a turn (<|im_end|>) at a colon or action declaration prior to outputting <tool_call>.
3. Multi-Turn Thinking Memory: Preserves historical <think> blocks across turns by default, preventing context distribution drift in 78K+ token runs.

Usage with llama-server:

llama-server -m Model.gguf --chat-template-file chat_template.jinja --reasoning-effort medium

<a id="toc-14"></a>

7. Community Compute Fund & Student Support

<a href="https://ko-fi.com/isvalorum"><img src="https://huggingface.co/spaces/IsValorum/MiniPlus-NanoPlus-Requests/resolve/main/assets/dance-gold-ship.gif" alt="Gold Ship dancing" width="128" align="right"></a>

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:

<a href="https://ko-fi.com/isvalorum"><img src="https://ko-fi.com/img/githubbutton_sm.svg" alt="Support on Ko-fi" height="38"></a>

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

<div style="clear: both;"></div>