◆ A personal interpretation of the narrative
The AI Builder Atlas
“Build 2026 was overwhelming. There was so much innovation it became easy to miss the larger narrative — how all of these pieces actually come together to productionise AI agents. This page is an attempt at interpretation of that narrative.”
One coherent throughline across the announcements: pick your intelligence, ground it, give it tools, run it safely, and place it on the right compute. Five builder layers, eleven sample tracks, one assembly line.
01 / THE MAP
From dev substrate to production harness
One diagram, read top to bottom. The four numbered blocks are the builder assembly line. The bands around them are the platform that makes the line run. See the layer-by-layer breakdown →
Dev / Backend Builder Substrate
Model
What intelligence do I use?
Context / Data
What does the agent know?
Tools
What can the agent do?
Harness
How does it run safely?
AI Infrastructure
02 / BUILDER JOURNEYS
Now read it sideways
The map above is vertical — layers you stack. Builder journeys are the horizontal cut: six end-to-end workflows that compose those layers into something you could ship. See all six journeys →
03 / PURPOSE
Announcements in, samples out
The atlas is the index. This repo is the workshop: a public-safe space that turns each Build 2026 capability into demos and implementation tracks a builder can ship. Three ways in:
→ 01
The Stack
Walk the five layers one at a time — what each decides, the Build 2026 updates inside it, and the sample that exercises it.
Open the stack → 02Samples
The opening backlog: eleven builder questions mapped to eleven concrete builds, each tagged to its layer, public source, and maturity.
Browse samples → 03Sources
The public Microsoft and GitHub material the atlas is anchored to — plus how private context stays local and off GitHub.
See the receipts