Maximum Friction to Copy a Person, Zero Friction to Act as One

Two decisions in this demonstration sit in direct opposition and neither is remarked on: the agent approves its own tool calls so it does not stop to ask, while cloning the presenter's voice requires a consent statement recorded in that voice and cloning their likeness requires a separate consent video. Maximum friction to copy a person, zero friction for the agent to act. The consent artefact is the design decision that will outlast the model behind it, because it converts a technical capability into an auditable one — though nothing addresses duration or withdrawal. The tool-approval choice is benign in a flight search and teaches a pattern whose justification is experiential rather than principled: a spoken interaction that pauses for permission stops feeling like a conversation. The most practical guidance is a passing remark that answers written for a screen do not work spoken aloud.

Microsoft Build

Jensen Huang's GTC 2026 Keynote: Vera Rubin, the Groq Deal and the Inference InflectionNVIDIA GTC · Mar 16, 2026138:56 Two Banks Went Opposite Directions on Identity, and Both WorkedAWS re:Invent58:44 PepsiCo's Six-Agent System for Account Managers, and What It Cost to BuildMicrosoft Build41:40 The Connector List Is the Product and the Risk SurfaceGoogle I/O12:31

35:13Huang's Five-Layer Cake: The Infrastructure Argument He Took to DavosHuang brings a diagram to Davos: AI as a five-layer cake running energy, chips, cloud, models, applications — with economic benefit landing at the top and every layer below it a precondition. His argument for why this is a genuine platform shift rather than a product cycle is the strongest part, and it does not rest on his commercial position: software was pre-recorded and worked on structured data, whereas a machine that reasons about unstructured input and inferred intent makes previously impossible applications possible. What the framing accomplishes is worth noticing separately. By presenting the layers as a chain rather than a portfolio, it converts infrastructure spending from a bet into a prerequisite, and the question of proportion between layer-two spending and layer-five value stops being askable. Read against the GTC keynote two months later, the same business gets two framings: one a case for choosing his product, the other a case for the category existing at the scale he needs.World Economic Forum Annual Meeting

60:00Escaping the Prompt-and-Pray Loop: Spec-Driven Development at re:Invent 2025The practical counterpart to the argument made elsewhere this season that specification is what contains model entropy. Raval and Harris name the failure they are addressing precisely — a prompt-and-pray loop in which working code arrives with no record of what the model assumed, which requirements were fuzzy, what design was chosen or why, leaving nothing to review and nothing to iterate against when a defect surfaces months later. Their answer is three committed markdown artefacts: requirements written in a structured requirements syntax with acceptance criteria attached to each user story, a design document carrying technical decisions together with the reasoning behind them, and a task list whose entries cite the requirement numbers they satisfy. The traceability is the point — a reviewer questioning a decision in a pull request can follow it back through the task to the design to the requirement, all in the same repository. Notably they keep the human between each phase rather than after it, with the agent surfacing ambiguity as questions before proceeding.AWS re:Invent

Editor's picks

PepsiCo's Six-Agent System for Account Managers, and What It Cost to BuildMicrosoft Build41:40 Huang's Five-Layer Cake: The Infrastructure Argument He Took to DavosWorld Economic Forum Annual Meeting35:13 Escaping the Prompt-and-Pray Loop: Spec-Driven Development at re:Invent 2025AWS re:Invent60:00 Where Agentic Coding Actually Breaks: Russinovich and Hanselman at Build 2026Microsoft Build46:52

Featured analysis

Great ideas deserve a great article.

Explore the ideas behind professional talks through clear articles, connected topics and references to the original sources.

Browse all intelligence

Explore by industry

Start with the fields where public summit knowledge can change a decision.

AI and enterprise technology Business, finance and investment Climate, energy and infrastructure Manufacturing and supply chain Built environment and materials

Bring your summit archive into the research record.

Share official agendas, recordings and corrections with our editorial team.

For organizers

How we index, verify and rank summit content.

Read the methodology