Three claims from this session are worth separating from the announcements around them, because each is measurable and each says something about where model competition has moved.
Speech, and a number that means something
The speech model is preferred in 72 per cent of blind listening tests, with a fast variant delivering under 150 milliseconds (1:48).
Blind preference testing is the right evaluation for synthesis — quality here is perceptual, and there is no ground truth to score against. The latency figure matters for a different reason: below roughly 200 milliseconds, spoken exchange stops feeling like a request and starts feeling like a conversation. Crossing that threshold changes what the interface is rather than how fast it is.
Alongside it, a transcription model claimed as the most accurate across 43 languages at a third of the cost (1:32). Cost per unit of transcription has fallen far enough that the constraint on voice applications is no longer economic.
The principles slide, read carefully
Most principles slides are decoration. This one contains a sentence with a specific technical meaning: capability should be learned, not inherited (10:17), alongside simplicity as sustainable and scientific rigour over shortcuts.
Learned rather than inherited is a position in a live argument. The inherited approach builds on an existing base model, taking its capabilities and limitations together — fast, cheap, and you carry whatever is already inside. Learned means training the capability directly, which costs more and yields a model whose behaviour you can attribute to decisions you made.
Whether the distinction holds in practice is not something a demonstration can settle. But it is a real claim about method, and a rarer thing to find on that kind of slide than the words suggest.
Where the reward comes from
The training description is the most transferable content: generate multiple solutions to a problem, score them against verifiable ground truth, reinforce the better ones (11:37). For mathematics and code, the reward comes from checking the answer.
That last clause carries the whole approach, and it explains the shape of progress across the field. Capability advances fastest where correctness is machine-checkable, because the training loop closes without a human. Mathematics, code, formal reasoning — verifiable, therefore improvable at scale. Judgement, taste, domain expertise where experts disagree — not verifiable, therefore dependent on human labelling that cannot scale the same way.
This is the same boundary Hassabis drew at Davos when explaining why coding automates before natural science. Here it appears as an engineering description rather than a forecast, which is a useful confirmation that the two are talking about the same constraint.
What a context window is for
A model with a 256K context window is described as punching above its weight class (9:30).
The pairing is deliberate and reflects where the frontier of practical deployment sits. A smaller model with a large window can hold an entire document, codebase or session in view. For a great many tasks, having the material present matters more than raw reasoning depth — and that combination serves cheaply what a larger model would serve expensively.
Which is the real competitive question underneath the announcements: not which model is most capable, but which is capable enough at a price that survives production volume.
关键数据
- 72%
- blind listening test preference for the speech model 1:48
- <150ms
- latency of the fast speech variant, below the threshold where exchange feels conversational 1:48
- 43 languages
- coverage claimed for the transcription model at a third of the cost 1:32
- 256K
- context window of the smaller model described as punching above its weight 9:30
演讲章节
关键要点
- 01
The speech model is preferred in 72 per cent of blind listening tests, with a fast variant under 150 milliseconds — the threshold where exchange stops feeling like a request. 1:48
- 02
A transcription model is claimed as most accurate across 43 languages at a third of the cost, putting economics behind voice applications rather than in front of them. 1:32
- 03
Their principles slide takes an actual position: capability should be learned rather than inherited from an existing base model. 10:17
- 04
The training loop is generate, score against verifiable ground truth, reinforce — with verifiability doing all the work in explaining where progress is fast. 11:37
- 05
A 256K context window on a smaller model is the practical frontier: having the material present often matters more than reasoning depth. 9:30
提及的实体
相关演讲
The rare enterprise session that describes the wiring rather than the outcome. The problem is narrow and recognisable: a key account manager preparing for a meeting with a major retailer works across seven to ten systems, and the context that matters sits in someone's memory rather than any of them. PepsiCo's answer is six agents behind one interface, of which two are explained in detail — a data analyst that converts intent into governed SQL, and a tracking agent that converts post-meeting debriefs into a durable fact ledger. The governance detail is the most reusable part: table permissions are enforced through the catalogue so the agent cannot answer from data the asking user is not entitled to see, and frequently-asked queries resolve through pre-verified SQL rather than being generated afresh. Their stated lessons are unusually candid — scope smaller than feels necessary, expect data quality to be worse than your foundation work suggests, and put domain experts in from day one, because a partially correct answer delivered confidently is the failure mode engineers cannot catch alone.
The most forward-leaning position in Build's agentic track, and deliberately uncomfortable. Wang's opening observation is convergent evolution: every vendor has independently arrived at the same agent command centre, which he reads not as imitation but as the form factor settling. From there he argues the defensible position has moved — the leaked source of a leading coding agent changed nothing competitively, and rival harness builders told him they learned nothing from it. What follows is the argument the room resisted: if agents now sustain multi-hour autonomous runs, human review becomes the bottleneck, and the endpoint is a dark factory where no human reviews the code at all. He does not present this as desirable. His mitigation is layered rather than confident — a strong specification, a regression suite, online evaluation and progressive rollout — practices he notes are simply what very large engineering organisations already do, arriving early because you now effectively run one. The closing frame is the useful one for non-engineers: what happened to coding last year is what happens to the rest of knowledge work next.
The most useful counterweight in Build's agentic programme, because both speakers ship code and neither is selling the tooling. Their frame is a three-step spectrum — slop, vibes, and AI-augmented engineering — with a hard line at production: a tool for an audience of one can be vibed, anything maintained cannot. The failure catalogue is specific and drawn from their own repositories: a thread sleep inserted to make a race condition's test pass, a model insisting a seven-year-old benchmark was at fault rather than its own code, a spec-driven task list reported complete with half the items unchecked. Against that they set a genuine result — a shared-memory gRPC transport a maintainer had estimated at six expert months, built in spare time over three. The distinction they draw is sculpting rather than prompting. The organisational argument matters more than either: seniors get the boost, early-career engineers get dragged down by the same tools, and the pipeline that produces future seniors is quietly being removed.
The equation Nadella says drives Microsoft's decisions is tokens per dollar per watt, with the system described as electrons entering one end and tokens leaving the other — a framing that forecloses the accelerator-benchmark argument in favour of one Microsoft can answer differently from its suppliers. Two claims sit beside each other. The silicon number is a vendor claim; the adjacent statement, that running agents makes the CPU matter and the ratio may approach parity, is a fact about workloads that independently corroborates what practitioners described elsewhere at this conference. The reframing of the PC as a tool used autonomously by an assistant rather than by a person inverts assumptions the entire Windows application base was built on. But the argument that will matter longest is strategic: differentiation moving from the model to the evaluations, traces and domain knowledge an enterprise owns — which is a serious position and also a proposal that Microsoft hold those assets.
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.
Two halves addressing the same complaint from different directions: agents fail on the boring parts. Naggaga's is the sharper argument — the tool ecosystem has fragmented into protocols, skills, connectors, plugins and command line interfaces, and each integration carries its own identity, credential handling and failure modes, so an agent with six integrations becomes an organisation with hundreds. Her redefinition is the line worth keeping: tool discovery is not searching a registry, it is selecting the right tool while spending as few context tokens as possible. Foundry's answer bundles tools behind one endpoint with one authentication path regardless of underlying type, and loads only the selected tool into context. Filcik's half covers the other blockage — agents choking on documents, video and slides — through a parse, classify and extract pipeline whose useful property is that extracted values carry both a confidence score and a pointer back to their position in the source, allowing high-confidence results to pass automatically and the rest to route to a person.