Hassabis steps back, Jeff Dean walks out the door

Hassabis steps back, Jeff Dean walks out the door

Good morning πŸ‘‹ Demis Hassabis just traded the corner office for a lab coat, and Google's shares didn't like it.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


πŸ”­ THE ONE THING

🧠 Hassabis steps back, Jeff Dean walks out the door

Sundar Pichai's memo reshuffles the top of Google's AI org: Demis Hassabis moves from CEO to Chair of Google DeepMind and the newly created Chief Scientist of Alphabet, ceding day-to-day control of Gemini and frontier research to Koray Kavukcuoglu, now SVP reporting straight to Pichai. Hassabis keeps Isomorphic Labs, so read this as a promotion into strategy, not a demotion. The more interesting exit is Jeff Dean's: 27 years in, he's out to co-found Discovery Loop with Sanjay Ghemawat, Oriol Vinyals, and Quoc Le, a public-benefit corp betting AI can run the hypothesize-experiment-evaluate loop of science on its own, with Google staying on as investor and cloud partner. For anyone building on Gemini, the org chart matters less than the fact that the guy who invented Bigtable, Spanner, and MapReduce just bet his next decade on automating science itself.


🧠 MODELS & RELEASES


πŸ”¬ RESEARCH HIGHLIGHTS


πŸš€ AI STARTUPS


πŸ› οΈ TRY THIS

Bake a verifier into your agent's output, not a bigger prompt

Hassabis just traded CEO for chief scientist. Read into that what you want, but the signal is rigor over speed. AWS shipped something in that spirit this week: open source Agent Skills that let a coding agent build, test, and deploy a formal verification policy for your own agent's outputs.

1. Point a coding agent (Claude Code, Q Developer, whatever you run) at AWS's new Agent Skills for Automated Reasoning and hand it a compliance doc or internal SOP.

2. Ask it to draft a Bedrock Automated Reasoning policy that encodes those rules.

3. Have it generate test cases, some that should pass, some that should violate the policy, and run them against the draft.

4. Read the counterexamples it surfaces. They usually mean your original doc was vaguer than you thought. Fix the doc, then deploy the policy as a guardrail.

Prompt: Read the attached compliance policy. Draft an Amazon Bedrock Automated Reasoning policy that encodes its rules, then generate 10 test scenarios, 5 that should pass and 5 that should violate the policy, so I can validate it before deploying.

πŸ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.