THIS WEEK'S MODEL: Gemma 4 26B MoE (Q4_K_M)
WHAT IT'S FOR: Frontier-quality local reasoning over long business documents — contracts, RFPs, board decks, financial statements, construction specs, vendor agreements.
WHY IT MATTERS: Gemma 4 is the first local model where the long context window is real. Gemma 3 advertised 128K but its information-retrieval rate at that length was a brutal 13.5%. Gemma 4 jumped that to 66.4% — and the new 26B MoE goes all the way to 256K tokens (~192,000 words, or a 500-page document). The Mixture-of-Experts design activates only ~4B of 26B parameters per token, so it punches at flagship quality (MMLU Pro 85.2%, GPQA Diamond 84.3%) while staying inside consumer-hardware reach. For our community, this is the model that finally makes "drop the whole contract in and ask questions" a sovereign, on-device workflow.
INSTALL:
ollama pull gemma4
RUN IT:
ollama run gemma4
TRY THIS PROMPT — "Monday Morning Document Triage":
You are a senior business analyst preparing my Monday morning briefing.
I am pasting a business document below. Produce a one-page brief with:
• TL;DR — three sentences. What is this document and what does it ask of me?
• KEY OBLIGATIONS — the top 5 commitments, deadlines, or deliverables, each with the exact section/page reference.
• DOLLARS & DATES — every specific dollar amount, percentage, deadline, and quantity, with context.
• RED FLAGS — any clauses, terms, or numbers that deviate from industry norms or that I should push back on. Be specific.
• QUESTIONS BEFORE I SIGN — three sharp questions I should ask the counterparty.
• NEXT ACTION — the single most important thing I should do today.
Do not summarize generically. Quote exact phrases when calling out risk.
DOCUMENT:
---
[ PASTE YOUR DOCUMENT HERE ]
---
HARDWARE REQUIREMENTS:
Minimum: 16 GB unified memory (Apple M1/M2/M3) or 12 GB VRAM (RTX 3060 / 4060 Ti 12GB) — ~12–18 tok/s, shorter contexts.
Recommended: 32 GB+ unified memory (M2 Pro/Max, M3 Pro/Max) or 16–24 GB VRAM (RTX 4080 / 4090) — ~25–45 tok/s, comfortable 64K–128K context.
Reference high-end: AMD Ryzen AI MAX+ 128 GB unified — ~85 tok/s, full 256K context loaded.
VRAM footprint at Q4_K_M is roughly 8–10 GB for the model, plus KV-cache that scales with context length (budget another 4–8 GB at 64K+). MoE means active params are small, so memory bandwidth (not compute) becomes the bottleneck — Apple Silicon and Ryzen AI MAX+ perform unusually well here.
ERIC'S TAKE: This is the model I've been waiting for. We've all built workflows that chunk documents into 4K-token slices and hope the model stitches them back together — Gemma 4 lets you stop doing that. Picture loading a 78-page MSA, a 40-page vendor SOW, and a stack of redline emails in one prompt and asking the model to reconcile the obligations. That's now in reach on consumer hardware. For the construction and finance folks in here, the implication is huge: your RFPs, your closing binders, your monthly board packets — they all fit in one shot, on your machine, with nothing leaving your desk. If you ran Week 1's Llama 3.1 8B and felt the context limit, this is your upgrade.
THIS WEEK'S CHALLENGE:
Pull gemma4. Pick one real document you'd normally upload to a cloud model — a contract, an SOW, a financial filing, a long email thread — and run the "Monday Morning Document Triage" prompt against it. Then post in the comments:
• What document type you tested.
• One thing the model caught that surprised you.
• Your hardware + tokens/sec.
Sovereign means the document never leaves your machine. Let's see what the room runs.