When Dependency Becomes Policy

Hosts: Lenar Kess, Damra Vol. Today’s episode starts with governments treating AI dependency as a policy object: search ranking rules, compute gaps, procurement choices, and summit politics all became part of the same operating problem for builders.The UK Competition and Markets Authority moved further toward conduct requirements for Google Search and AI Overviews, putting ranking and self-preferencing directly into the AI search conversation.The European Commission’s Digital Decade report framed Europe’s digital capacity gaps as an investment and dependency problem rather than only a competitiveness scorecard.The Guardian’s France reporting gave the policy story a concrete procurement example: moving away from Palantir toward domestic tooling.Fireworks AI, Parasail, and other providers turned GLM-5.2 into a day-zero availability story, with claims around long context and coding benchmarks that developers still need to test in their own loops.Qwen-RobotNav and MuseVLA show physical AI moving toward reconfigurable navigation, sensor selection, and embodied evaluation rather than demo-only robotics.The Rift deception paper offers a useful safety-research coda: internal signatures may help separate a model that is wrong from a model that is hiding what it knows, with caveats the authors state plainly.