The Adjacent Brief

TL;DR: Search Engine Journal published data showing AI assistants recommend one set of brands while citing websites that promote a different set, and that model preference now varies sharply by age — Gen Z picks Claude over ChatGPT by more than seven to one. Google moved DeepMind's roughly 90-person AI responsibility team into its global affairs unit. Nvidia is pitching edge deployments as its next multibillion-dollar market as data center projects face delays.

Worth Reading

The New Consumer

The AI recommendation layer doesn't match the citation layer, and that breaks the SEO playbook

Search Engine Journal's data shows AI tools recommending brands that the sites they cite don't actually recommend — the model surfaces one answer, footnotes a source that says something else. For anyone who has spent the past eighteen months buying "AI visibility" consulting, this is the load-bearing assumption collapsing. The citation is decoration applied afterward, independent of the actual reason for the recommendation. The strategy of getting placed on the sites that models cite doesn't reliably move what models say. The interface presents provenance, but provenance isn't driving the output. Practical read for a CMO: stop paying for citation-count dashboards until someone demonstrates the link between citation and recommendation. Right now the vendors can't.

Model preference is splitting by age, which turns AI visibility into a segmentation problem

The second dataset out of Search Engine Journal finds Gen Z favoring Claude over ChatGPT by more than seven to one, while older cohorts skew the other way. Treat this cautiously — it's preference data, not behavioral share, and preference surveys have overstated switching before. But if it holds, the operational consequence is concrete: brand answers now differ by which model your customer opened, and the models differ by age. A single "how do we show up in AI" workstream becomes two or three, with different retrieval behaviors and different training corpora behind each. Anyone benchmarking their brand's AI responses against one model is measuring one demographic.

Quieter voices, louder machines

A curious adjacent finding: researchers report that people are literally speaking more quietly than previous generations, with measurable declines in vocal volume and projection. File it next to the UK GP surgery that pulled its AI receptionist after it failed to understand a stroke patient. Voice interfaces are being designed against an assumption of clear, loud, unaccented speech that a shrinking share of the population actually produces. The core accessibility risk in 2027 voice interface roadmaps reflects the experience of the median user rather than an outlier.

Brand & Growth

Token costs are a margin problem that companies misread as an infrastructure story

The Next Web's piece on the rising costs of the token consumption race is worth reading against the reflex it invites. AI product companies priced their subscriptions before agentic workflows multiplied per-user token draw by an order of magnitude, leaving the aggregate compute bill as a secondary concern. Fixed price, variable and rising cost of goods. That's a gross-margin structure, and it's the reason you're seeing usage caps, credit systems, and "fair use" language appear across tools that launched with unlimited plans a year ago. The adjacent data point: Microsoft employees reportedly spend a median $300 a month of their own money on external AI tools. Demand at the individual level is real and price-insensitive. The question is whether that survives contact with usage-based billing.

Moving the ethics team to global affairs tells you what the function is for

Google is relocating DeepMind's roughly 90-person AI responsibility group out of the research lab and into the global affairs unit (paywall), per an internal email obtained by the Wall Street Journal. Org charts are strategy documents. Inside DeepMind, that team's outputs shaped what got built and shipped. Inside global affairs, its outputs shape what gets said to regulators. Those are different jobs with different success metrics, and the reporting line determines which one the group optimizes for. Note the timing: this comes as regulatory pressure in the EU and several US states is intensifying, which is precisely when a policy-facing responsibility function is most useful to a company and least useful as a product brake.

Connected World

Nvidia's edge push is a hedge against data centers that don't get built

Nvidia is positioning distributed AI compute outside the data center as its next multibillion-dollar market — factory floors, hospitals, retail backrooms, vehicles. Read this alongside Kimmeridge's estimate that half of proposed US data center projects face delay or cancellation, mostly on power interconnection and local permitting. Nvidia's centralized demand curve has a physical dependency it doesn't control: grid capacity and county zoning boards. Edge deployments route around both. They also change the sales motion from a handful of hyperscaler buyers to thousands of enterprise ones, which is harder but far less concentrated. For anyone selling into infrastructure, compute placement is becoming a siting and energy question before it's a technology question.

A wooden car seat is a materials-sourcing bet — and sustainability is beside the point.

BMW built a car seat structure out of wood, and the reflex is to file it as green marketing. The more useful frame: automotive interiors are one of the last places where petrochemical inputs and steel substructures still dominate, and both carry volatile pricing and carbon-accounting liabilities that show up in European regulatory filings. A structural material that's cheap, locally sourceable, and doesn't require a supply chain running through geopolitically exposed regions is a cost hedge dressed as an eco-story. Whether it survives crash testing at scale is the actual question. The motivation isn't the press release's.

Culture & Signal

A settlement that requires the technology to work is a settlement that hasn't settled

Meta's $18 billion child-safety agreement depends on age-verification systems with documented accuracy problems, particularly at the 13-to-17 boundary where the consequences matter most. The structure of the remedy is the story: to keep minors safe, platforms must collect identity documents or facial scans from everyone, including the minors. Regulators got a headline number and an enforceable-sounding mechanism; users got a new category of sensitive data sitting in a new set of databases. Age-verification friction is showing up across jurisdictions the same way: the mandate arrives fully formed, the technology arrives approximately, and the gap between them becomes a data-collection liability nobody underwrote. For platform operators, the planning assumption should be that verification requirements expand faster than verification accuracy improves, and budget for the breach.

Machines & Minds

Governance frameworks are auditing everything except the decision

Forrester's argument is blunt: enterprises building agent governance are controlling the infrastructure around agents while leaving the agents' own reasoning ungoverned. Access controls, API permissions, logging, sandboxing — all mature, all necessary, all beside the point when the failure mode is an agent making a defensible-looking decision that's wrong. Pair this with Google's reorganization of its responsibility team: the governance function keeps getting placed adjacent to the thing it's supposed to govern rather than inside it. Concrete ask for anyone standing up an agent program — if your governance artifact is a permissions matrix, you have infrastructure governance. Ask what happens when the agent is fully authorized and still wrong.

The boring deployments are the ones with a value loop

Waystar has pointed agentic systems at claims processing, denial appeals, and clinical documentation — the least demo-friendly workflow in healthcare and one of the most expensive. This is the shape worth paying attention to: a repeatable task, a measurable dollar output per completion, and a customer who already tracks the metric. Denial rework has a known cost per claim, so the ROI calculation is arithmetic rather than narrative. Contrast with the generic agent pilots stalling inside enterprises because output volume outpaces the humans available to review it, a review bottleneck that surfaces repeatedly, where agents generate more work than they remove. Waystar's advantage lies in pairing its automated agents with a reviewing party that is itself an insurer running its own automated process. When both ends of the loop operate at machine speed, agents compound. Where a human sits in the middle, they queue.


10 articles across 5 themes · 8 sources · Powered by Folo + Claude