Notable verbatim quotes

All quotes preserve speech-to-text artifacts (e.g. "8x" ≈ "AX", "mid structure" ≈ "machine-structured", "AI navy" ≈ "AI native") — do not silently correct.

The expanded builder persona

• "Oh man we ain't precious no more y'all the builder persona has changed the person our platforms were built for are no longer just developers" — §2
• "the IDC predicts that more than 500 million your applications will be built by 2028... 40 years have been compressed into three" — §2
• "agents have turned intent into a programming language in fact the strongest programming language that will happen now and into the futures guess what? English" — §2
• "it's therapists teachers small business owners students people in line at the store building experiences on their phone... and becoming software creators" — §2

The AX paradox

• "when we designed our platform to work better for agents serving these new builders it got better for developers too. And that's the 8x paradox." — §2
• "Every human assumption we remove made the platform better for everyone this is the gap of what we call agent experience." — §4
• "design for agents. Actually was designing for humans all along." — §4
• "Turns out redesign for everyone. Is the agent experience not designing for agents." — §15

What AX is

• "agent experience isn't about making machines happy it's about removing that friction every step of the way so that you can get from I give into reality" — §5
• "It is the practice of designing where humans and agents collaborate seamlessly. And it isn't just about making API API calls agent friendly. You really do have to rethink the entire stack" — §5
• "you've all heard user experience we heard in 2012 Jeremiah leafed Spotify coin developer experience and my boss Matt Biemann last year said you know what the new paradigm is agent experience" — §5

Structured errors / build logs

• "our build logs used to be human readable narratives great for scanning, great for dev ops... terrible terrible for agents" — §10
• "We restructured them into mid structure machine readable error codes alongside that human text. And agent can now parse a build failure identify a misunderstanding fix it automatically." — §10
• "that same structured output made our dashboard clearer for human engineers too" — §10

APIs → capabilities

• "An agent looking at a 200 endpoint API surface has to figure out the right context, the right sequence, the right parameters in the right order." — §11
• "Agent native systems expose these intent level operations. Create a site... deploy repository. Provision edge compute. These are capability agents can reason about." — §11
• "we've evolved our API service to support both modes traditional rest for existing integrations and capability based interfaces for agent interactions" — §11

Event-driven

• "Traditional APIs are full based. You send a request, get a response. Agents have to pull guest retry. AI navy systems expose events." — §11

Blueprints / legible architecture

• "Critical workflows live and tribal knowledge and in someone's head in a slack thread from 2022 in an undocumented terraform module" — §11
• "This is why we created our system of record called blueprints. Yes this is skills, context and recipes... The architecture decision records all design so coding agents understand the system for they make the changes." — §11
• "The goal isn't better documentation. It's ensuring agents can operate safely and complex systems." — §11

Trust principles

• "Trust has to be default and is not optional. We have three principles... first sandbox execution... Second human in the loop by default... and third audit rollback every agent action is logged" — §12
• "the agent builds the human approves" — §12
• "If you can't explain what the agent did why would you trust your production?" — §12

Code is no longer scarce

• "when anybody can generate software code is no longer the scarce resource... Now the scarce source becomes taste. Know what's worth building judgment." — §15
• "the judgment to build systems agents can work with that is the engineering skill of the future" — §15

Ship-tomorrow takeaways

• "Go fix your structured errors. Go create event driven signals and logical architecture... go learn how to write your damn skills because your job depends on it." — §14

On environmental impact (Q&A)

• "the bitter truth is you're going to be stuck building a whole bunch of stuff that's going to be obsolete" — §16
• "We have to burden that responsibility on our shoulders to make sure that we are implementing compaction... compression... building the right resources to make the internet continue to be open and democratized... But also the environmentally friendly." — §16