Quick Navigation Index

1. Optimization History & Transparency Notice
2. Independent Benchmark of the APEX-I-MiniPlus Family (Occamy V2 Reference)
3. Empirical Benchmarks & Fidelity Verification
4. Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Flat Quantizations
5. Model Files & Technical Specifications
6. Surgical Tensor Quantization Map (Audited from GGUF)
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. Recommended Generation Parameters (apodex Official)
11. CRITICAL: Coding Syntax & Repeat Penalty Advisory (Preventing Character Swapping)
12. Hardened Agentic Chat Template & Reasoning Effort
13. Optional Support

Apodex-1.1-mini APEX-I-MiniPlus-V2.1 GGUF

The Definitive Frontier MoE · Efficient System RAM Offload · Full 256K Context on 24GB Workstations

[!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 13–14 GB 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.64 (Reference)	Full precision baseline
APEX-I-MiniPlus V2.1 (CURRENT)	15.30 GB	14.25 GiB	3.40 BPW	5.7073 ± 0.1373 (approx. ΔPPL +0.0673 / +1.19%)	Q5_K_M tier

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 (whether V1, V2, or V2.1), 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 reasoning models, this triggers severe perplexity spikes, syntax errors, and broken code brackets.
• Handcrafted APEX-I-MiniPlus (All Editions by IsValorum): Every single MiniPlus release—from V1 and V2 to V2.1—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). Even our earlier builds vastly outperform generic community APEX recipes and flat 3-bit quants.

[!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.

---

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:

[!TIP]

Architecture & Edition Guide — Choosing Between Editions

• Full GPU VRAM Offload (24GB+ VRAM, -ngl 99): Both V2 and V2.1 run blistering fast on GPU tensor cores with virtually identical top-tier quality.
• In Practical Long-Context (+160K tokens): Although V2 provides higher theoretical protection on paper, real-world benchmarks show virtually zero perceptible quality difference compared to V2.1 even across deep +160K contexts.
• System RAM Streaming Specialist (DDR4/DDR5 & Massive Context): V2.1 is specially engineered to run either partially or entirely out of system RAM across large or full (+160k to 256k) context windows. By replacing non-linear codebooks with linear SIMD-optimized Q3_K edge experts and upgrading shared foundation experts to Q5_K across all 40 layers, AVX2 CPU dequantization stalls are completely eliminated. Depending on your processor architecture and memory bandwidth (dual-channel DDR4 or high-speed DDR5 6000+ MT/s), streaming generation speeds in system RAM can approach speeds remarkably close to full VRAM execution, allowing GPU VRAM to remain dedicated to the extensive research KV cache while scientific synthesis weights stream efficiently from system RAM. The approx. 100 MB difference over V2 is completely negligible when running in system RAM.

Both editions are handcrafted and vastly outperform flat 3-bit quants and generic community APEX-I-Mini releases.

Prefer high theoretical edge layer protection on paper? Explore the Apodex-1.1-mini MiniPlus V2 Edition.

---

[!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.

---

🏅 Independent Benchmark of the APEX-I-MiniPlus Family (Occamy V2 Reference)

[!NOTE] External report: zephel01 independently benchmarked Occamy V2. The benchmark below was performed on Occamy-1.0 APEX-I-MiniPlus V2, not on this specific V2.1 model. It is included as independent evidence of the broader MiniPlus quantization approach.

The APEX-I-MiniPlus quantization architecture powering this model was subjected to an extensive independent evaluation by Japanese AI researcher and evaluator zephel01 (CoolZero) on an NVIDIA RTX 5090 (32GB) workstation running llama.cpp CUDA b11027 with FlashAttention (-fa on -ctk q8_0 -ctv q8_0 -ngl 99).

The evaluation tested the APEX-I hybrid MoE engine across 348 unseeded trials on SWE-bench style multi-file Python bug-fixing tasks with hidden pytest suites (llmbench):

• L6 Multi-File Code Generation (60 tasks):
  • Context 32,768 (32K): 93.3% Resolved (46/60 tasks passed 5/5 consecutive trials; 20/20 on Easy–Hard).
  • Context 65,536 (65K): 90.0% Resolved (45/60 tasks passed 5/5 consecutive trials).
  • Match with 25–28 GB Models: Matches or exceeds the resolution rate of full 25–28 GB models (such as Ornith-1.5 and Tiel-Coder 35B-A3B) while consuming over 10 GB less VRAM (14.6 GB vs approx. 26 GB).
• Extreme Context VRAM Scaling (The Hybrid DeltaNet SSM Advantage):
  • 32K Context: 14.6 GB total VRAM allocation.
  • 65K Context: 15.1 GB total VRAM allocation (only +0.5 GB VRAM added when doubling context!).
  • Architectural Explanation: Because 30 of the 40 layers utilize Linear Attention / DeltaNet SSM ($O(1)$ constant recurrence memory), only the 10 full-attention anchor layers expand the KV cache. This proves empirically that 65,536 context runs 100% in VRAM on consumer 16GB GPUs (RTX 4080 / RTX 5080) without offloading to system RAM.
• Measured Real-World Throughput: Sustained single-stream generation of approx. 247 – 251 tok/s on NVIDIA RTX 5090.

---

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.

Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Flat Quantizations

How the handcrafted APEX-I-MiniPlus V2.1 architecture compares against standard flat quantizations in llama.cpp on 35B Mixture-of-Experts architectures:

Model Files & Technical Specifications

• Base Model: apodex/Apodex-1.1-mini
• Parameters: 35.2B total (approx. 2.6B to 3.2B active per token)
• Architecture: 40 layers, 256 micro-experts (8 active per token) + hybrid linear attention / DeltaNet recurrent layers
• Context Length: 262,144 tokens (native 256K)

---

Surgical Tensor Quantization Map (Audited from GGUF)

The exact tensor breakdown below has been verified directly from the compiled binary weights:

---

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

Empirically verified in Unsloth Studio & llama.cpp:

• Aggressive Hybrid Offload Profile: Hybrid offload supports reasoning-enabled generation with limited VRAM while the remaining model weights stream from system RAM.

[!NOTE]

Empirical Testbed Architecture & Desktop/Server Scaling

• Empirical Benchmark Hardware: The hybrid offload and system RAM streaming behavior documented above was measured on a consumer laptop powered by an Intel 12th Gen Alder Lake architecture featuring a hybrid design of Performance Cores (P-Cores) and Efficient Cores (E-Cores) paired with dual-channel system RAM and constrained laptop power/thermal envelopes.
• Thread Scheduling & E-Core Contention: In hybrid architectures like Alder Lake, OS thread scheduling across background E-Cores and lower single-core mobile power limits introduce memory bandwidth and thread synchronization overhead during CPU dequantization.
• Dramatic Scaling on Higher-End Processors: When running on desktop or server processors (such as modern AMD Ryzen 7000 / 9000 Zen 4/5 series or high-TDP Intel desktop platforms with dedicated performance cores, large L3 caches, and high-bandwidth dual- or quad-channel DDR5 running at 6000+ MT/s), streaming generation speeds and prefill throughput will scale dramatically higher, substantially exceeding these measured mobile numbers.

---

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

Apodex-1.1-mini 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).

[!TIP]

💡 Empirical 16GB GPU Verification (Single Stream / Desktop)

While theoretical multi-slot server buffers estimate approx. 16.5 GiB, independent hardware testing by zephel01 on an RTX 5090 (Occamy V2 Reference) confirmed that single-stream desktop inference consumes only 14.6 GB at 32,768 ctx and only 15.1 GB at 65,536 ctx (-ctk q8_0 -ctv q8_0 -fa on). This empirically proves that full 65K context runs completely in VRAM on 16GB cards (RTX 4080 / RTX 5080) without system RAM offload!

---

Recommended Configuration & Setup

llama-server.exe \
 -m Apodex-1.1-mini.APEX-I-MiniPlus-V2.1.gguf \
 --port 8080 \
 --parallel 4 \
 --flash-attn on \
 --fit on \
 -c 104960 \
 --cache-type-k q8_0 \
 --cache-type-v q8_0

⚙️ Recommended Generation Parameters (apodex Official)

Official generation hyperparameters specified by apodex for autonomous agentic workflows and tool-calling loops:

[!IMPORTANT]

🔍 Model Inherent Behavior vs. Quantization Fidelity Notice

Any behavioral nuances, stylistic tendencies, domain-specific 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.07), ensuring that token logits, routing decisions, and reasoning trajectories are mathematically faithful to the original base model.

[!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.

[!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

Optional Support

If these MiniPlus or NanoPlus releases have been useful to you and you would like to support the work, you can do so voluntarily through https://ko-fi.com/isvalorum. Your contribution helps with evaluation, hosting, and future handcrafted quantizations. Every release will always remain free to download and use; there are no paywalled files, updates, or features.