## Purpose of This Document This is a working curriculum, not a briefing memo. It exists to get one executive (leading enterprise AI transformation across a large technical and professional workforce) to a level of technical fluency sufficient to do five things without relying on a translator: set AI investment and architecture strategy; challenge vendors and internal technical teams with informed, specific questions; redesign how software gets built and how knowledge work gets done; manage the security, governance, and compliance exposure that agentic AI introduces; and measure whether any of it is actually producing business value rather than activity. It is explicitly not a path to becoming a machine learning engineer or researcher. Model architecture, training mechanics, and research-frontier mathematics are out of scope by design. What is in scope is everything a technically serious executive needs to make defensible decisions and ask the questions that make technical teams uncomfortable in a useful way. ## How This Document Is Organized The bulk of the document is a topic catalog: 80 topics across 20 domains, each written to a fixed template (definition, why it matters, what to understand, questions to ask your team, technologies to know, recommended learning, time investment), plus a 21st domain (an Emerging Technology Radar) covering 28 developments that are real but not yet decision-relevant, tracked so they don't arrive as a surprise. Every topic carries a priority tier, and the tiers are meant to be taken literally: **Must Understand**: you should be able to explain this to a peer executive and to your board without notes, and you should be uncomfortable delegating the underlying decision entirely. **Should Understand**: you need working knowledge deep enough to evaluate a recommendation from your team, but the day-to-day mechanics are theirs to own. **Monitor**: track directionally. Don't build expertise here yet; build the habit of checking back on it quarterly. 54 topics are Must Understand, 18 are Should Understand, and 8 are Monitor: reflecting a deliberately curated catalog rather than an exhaustive one. Everything included here already cleared a bar; if it's in this document at all, it's more likely to matter than not. A separate synthesis section, the 90-Day Executive AI Learning Plan, sequences this material into a realistic 3-5 hour/week study plan across three phases: Foundations (Days 1-30), Architecture & Transformation (Days 31-60), and Scaling the Enterprise (Days 61-90). If you read nothing else in this document, read that plan and the Top 25 Concepts cheat sheet that follows it. ## Three Questions This Document Is Built to Answer **What do I personally need to understand?** The topic catalog and the 90-Day Plan, in that order. Start with the Must Understand tier in Domains 1-4 (strategy, agents, Model Context Protocol (MCP), software engineering): that is where the largest, least reversible decisions sit in 2026. **What capabilities does my organization need to build?** The Enterprise AI Capability Model at the end of this document maps 15 capability areas (from AI platform architecture to workforce transformation) across four maturity levels. Use it as a scoring instrument, not a reading list: most organizations at your scale are Level 1 or 2 in most areas, and that is normal, not alarming, in September 2026. **What should I watch now versus later?** The Executive Technology Radar table converts the topic catalog and the emerging-technology radar into a single view: current importance, 2-3 year potential, and a recommended action: Adopt, Build Capability, Experiment, Understand, or Monitor. Not everything in this document earns "Adopt." Several genuinely promising developments (autonomous coding agents with merge authority, agent-to-agent commerce, fully autonomous business departments) are still speculative enough that the correct action is to watch, not to fund. ## A Note on Certainty This document distinguishes, deliberately and repeatedly, between what is established (DevOps Research and Assessment (DORA)'s research on AI-assisted engineering, National Institute of Standards and Technology (NIST)'s risk management framework, the Open Worldwide Application Security Project (OWASP) Large Language Model (LLM) Top 10), what is directionally clear but still moving (the EU AI Act's implementation timeline, agent identity standards, MCP governance), and what is genuinely speculative (autonomous departments, agent-to-agent commerce, embodied AI at enterprise scale). Where a claim is a prediction rather than a documented fact, it is flagged as such. Vendor marketing, consultant thought-leadership, and SEO content were deliberately excluded as sources in favor of primary documentation, standards bodies, peer-reviewed and preprint research, and named engineering organizations disclosing their own data. Every factual claim in this document links to its source. ---