Software people run. We file a tool when a workflow changes: how a model is served, indexed, or evaluated.
Nothing filed on this shelf in the current briefing.
A model release becomes useful when it has a way to run. EmbeddingGemma 2’s post names the paths that matter for that kind of model: transformers, MLX, llama.cpp, Ollama, vLLM, and a vector store. Carbon-A’s post names a Hub repo and an explorer. Those are tools, and they belong beside the weights.
Coding agents, local inference, and evaluation harnesses are standing categories. A new wrapper with a waitlist is not, unless it changes who can do the work.
The split we keep an eye on is where the bytes go. A 740-million-parameter embedder that runs in a few hundred megabytes of RAM makes private retrieval a local feature. A frontier assistant that builds a user interface still runs in the lab’s cloud. Both can matter in the same week. They are not the same deployment story.