Decision models just got their Ollama — the category now has a runtime, a rival, and a Pokemon demo.
Top Signal
Ollaya brings one-command local serving to Jev-style decision models
new tool
HN Front Page, r/LocalLLaMA
Ollaya is an Ollama-equivalent for open decision models — the Jev class that emits a decision per forward pass instead of streaming tokens. It hit 283 points on HN with 85 comments the same day r/LocalLLaMA published a Jev vs. Kev head-to-head and a Show HN put Jev through Pokemon Red. Until now, running an open Jev alternative meant hand-rolled inference (Von's 395M drop-in, Laya on OpenVINO int8); a packaged runtime plus model registry is the inflection where a category becomes usable by people who aren't studying it. Do this: find the lowest-latency step in your product that currently burns an LLM call — intent routing, tool selection, moderation gating, state-machine transitions — and prototype it as a decision model this week. Decisions-per-second on a laptop beats tokens-per-second in the cloud for anything that isn't generation. Read the Jev vs. Kev numbers before committing to a model.
Read more →
Fast Signals
Swift1.5 fine-tune cuts Qwen3.8 Flash-Next's excess reasoning
new tool
r/LocalLLaMA
A community fine-tune (ukisai/Swift1.5-Qwen3.8-Flash-Next) targets the one complaint that keeps resurfacing about Qwen3.8 as a Claude replacement: it thinks far too long. The poster reports a large reduction in wasted reasoning with quality intact. If Qwen3.8 is already in your local coding loop, swap it in and measure thinking tokens per completed task before and after.
Link →
KV cache transplants lift Qwen3.8-27B quality with zero retraining
research to practice
r/LocalLLaMA
Precomputed KV-cache blocks injected at inference time to steer output quality — no weight edits, no fine-tune, no training run. This is the second sighting of cache-as-configuration in five days after the 18MB KV bank experiment. It is the cheapest quality lever available to anyone who controls their own serving stack, and it composes with quantization.
Link →
Go experiments with platform-independent SIMD
platform change
HN Front Page
Go's new experimental SIMD API compiles to native vector instructions across architectures without per-arch assembly. If you write Go for tokenizers, embedding math, or vector search, this removes the main reason to drop into cgo or hand-written asm. Experimental, so read the blog post for the stability caveats before you build on it.
Link →
Hindsight: open-source agent memory that learns from outcomes
new tool
GitHub Trending
Vectorize's Hindsight is an agent memory layer that updates from what happened rather than just storing and retrieving transcripts. It is the third distinct agent-memory architecture to trend in a week, after lossless-memory's never-summarize approach. Worth a bake-off if your agent keeps repeating the same mistakes across sessions.
Link →
NVIDIA ships one library for quantization, pruning, and spec decoding
new tool
GitHub Trending
Model-Optimizer unifies quantization, distillation, pruning, neural architecture search, and speculative decoding behind one API, exporting to TensorRT-LLM and vLLM. Not novel research, but it collapses five separate toolchains into one dependency. Bookmark for the day your self-hosted inference bill becomes the problem you are actually solving.
Link →
stable-diffusion.cpp extends to Wan, Qwen Image, and Z-Image
new tool
GitHub Trending
Pure C/C++ diffusion inference with no Python and no CUDA runtime, now covering video (Wan) and the newer open image families. That makes image and video generation something you can ship inside a desktop or edge binary instead of a GPU service. Relevant if you have been assuming generative media requires a hosted API.
Link →
Someone finally published the H200 buy-vs-rent math
emerging signal
r/LocalLLaMA
An r/LocalLLaMA post shows the actual break-even working for buying versus renting an H200 box, and the author says the answer landed somewhere they did not expect. Local hardware capex has now trended four of the last seven days with no numbers attached; this is the first post with a spreadsheet. Steal the model structure before your next GPU decision.
Link →
Radar
Qwengram-0.8B: n-gram memory transplant on Kaggle GPUs
A dev moved Qwen3.8 Flash-Next's pretrained PLE n-gram memory into a 0.8B model and cut validation perplexity 5.05%, trained mostly on free Kaggle notebooks. Cross-model component transplant on a hobbyist budget is a technique with a lot of unexplored surface.
Link →
Mica 4B mines iron in Minecraft, zero tokens
A 4B action model completed a long-horizon crafting chain in real Minecraft without generating a single token. Evidence the decision-model class handles multi-step control, not just fast classification — the thing that would make it interesting for agent loops.
Link →
git-bug: issues stored in git, no API needed
A distributed, offline-first bug tracker that keeps issues as native git objects instead of rows in someone's SaaS. For agent workflows this means a coding agent can read and write the backlog with plain git and no credentials or network.
Link →
Self-decrypting HTML page for air-gapped files
Encryption packaged as a single self-extracting HTML file — recipients need only a browser, no tooling and no service. Useful primitive for handing artifacts or secrets to someone whose environment you do not control.
Link →
Convergence Watch
jev
TRENDING
3 mentions across HN Front Page, r/LocalLLaMA
Seven straight days of coverage, but today's mentions changed kind rather than volume: a serving runtime (Ollaya), a competitive alternative (Kev), and a non-trivial demo all landed at once. That is the pattern of a category stabilizing into a stack, not a hype cycle peaking.
decision models
TRENDING
4 mentions across HN Front Page, HN Show, r/LocalLLaMA
Ollaya, Kev, Mica 4B, and the Pokemon demo are four independent efforts around models that emit actions instead of text. The abstraction is escaping the Jev brand name, which is the moment a technique becomes a category you should have an opinion about.
qwen3.8
TRENDING
5 mentions across r/LocalLLaMA
Five mentions today across fine-tunes, KV-cache work, memory transplants, and Claude-replacement reports — but all from one source. Treat as a strong r/LocalLLaMA consensus rather than cross-source convergence. The repeated theme is fixing verbosity, not questioning capability.
local hardware capex
TRENDING
1 mentions across r/LocalLLaMA
Fourth appearance in seven days, and the first with actual break-even arithmetic instead of vibes. The recurring question underneath is whether displacing API spend with owned GPUs pencils out — a build-versus-rent decision that is now being argued with numbers.