Agentic Engineer — A Definitive Book and Ecosystem for the Agent Era

The Third Era of AI Tools

Agentic Engineer

A canonical source for the Third Era of AI Tools — delivered through a four-channel ecosystem: the book, an AI tutor, an AI building partner, and a growing family of specialized derivative books.

The spec-driven, human-supervised method for building AI-Native Companies. For engineers, domain experts, and enterprise leaders building the workforce of the Agent era.

📖 Canonical = the authoritative source. The one master version everything else is built from.

What This Is

It is 8 :07 a.m. A project manager is behind on a report. A finance lead is reconciling numbers across systems that don't talk to each other. A team is waiting on an answer that should have arrived yesterday. Now imagine each of them simply handed that work to a tireless digital coworker — one that follows instructions, uses the same tools they do, checks its own work, and hands back something they can trust. Building and directing that coworker is what this book is about.

A few plain words first, because the whole book leans on them:

An AI Worker (also called a Digital FTE — "full-time equivalent," the HR term for one employee's worth of work) is an AI that does a real job, not just answers a question. Picture a new hire who never sleeps: you tell it what to do, it does the work, and a human still signs off.

A general agent — tools like Claude Code, Claude Cowork, or ChatGPT — is the all-purpose assistant you direct. You either use it to get your work done, or use it to build one of those AI Workers.

An AI-Native Company is what you get when one founder runs a real business with a handful of people and many AI Workers, instead of a large staff.

That is the whole idea. Everything else is how to do it well.

This book is not about chatbot tricks, impressive demos, or short-lived prototypes dressed up like strategy. It is about building dependable AI workers that can participate in real business operations. These systems do not replace human judgment. They extend it, scale it, and make it repeatable.

In this book we introduce the concept of a Digital FTE (Full-Time Equivalent employee) — AI agents that can perform real work inside organizations, just like a human employee. In traditional organizations, an FTE represents the work capacity of one full-time human employee. A Digital FTE is the AI equivalent: an intelligent agent or digital worker that can perform tasks, execute workflows, analyze information, and assist teams inside real organizational systems. Unlike human employees, Digital FTEs can operate continuously, scale instantly, and be deployed in large numbers. As AI systems mature, organizations will increasingly build teams composed of both human employees and Digital FTEs working together — forming hybrid workforces that combine human judgment with machine intelligence. This workforce forms an AI-Native Company.

A note on terminology. Throughout this book, the terms Digital FTE , Digital Worker , and AI Worker are used interchangeably. They

The Five-Layer Cake of AI

all name the same thing: a role-based AI agent that performs structured work inside an organization, under human oversight. The thesis uses AI Worker as its technical term; this book uses Digital FTE as its business-facing term.

Modern AI is built like a towering five-layer cake — a metaphor popularized by Jensen Huang , CEO of NVIDIA . At the base lies Energy , powering vast data centers around the world. Above it sit Chips , the specialized processors that perform trillions of calculations every second. On top of that comes Infrastructure — the global network of supercomputers and cloud platforms that scale those computations. Above the infrastructure are Models , the neural networks that learn, reason, and generate intelligence. And finally, at the very top, sits the fifth layer: Applications — where AI stops being technology and starts becoming useful.

Billions of dollars are invested in the lower four layers so that this fifth layer can exist. This book is about that fifth layer. It teaches you how to build the applications, agents, and digital workers that transform AI capability into products people use, workflows organizations rely on, and value enterprises can capture.

The lower layers matter because they make the top layer possible. Models, infrastructure, and hardware are essential, but they do not create business value on their own. Value appears when intelligence is shaped into workflows, products, services, and operational systems that people can actually use.

The next competitive gap between organizations will not come only from who has the best model, the biggest GPU cluster, or the flashiest prototype. It will come from who can turn intelligence into repeatable execution. In the same way that software transformed manual processes into digital systems, Digital FTEs will transform structured knowledge work into scalable operational capability. The organizations that learn to build them well will move faster, preserve expertise better, and create entirely new forms of leverage.

The mission of Agentic Engineer is to help you design and build these systems — so that AI becomes not just powerful, but useful, governable, and economically meaningful.

The Core Idea

At the center of this book is a simple idea:

Digital FTEs — also called Digital Workers — are reliable AI agents designed to perform structured knowledge work continuously inside real organizational environments.

A Digital FTE is not just a model with a prompt. It is a system. It combines domain expertise, explicit specifications, engineering architecture, and human oversight so that work can be performed consistently, auditably, and at scale.

Agentic Engineer introduces a systematic approach for designing and deploying Digital FTEs — AI agents that transform human expertise into scalable digital workers. Working together they form an AI-Native Company.

Rather than focusing only on large language models, this book explains how dependable agent system

The System of Record for Education

s emerge from the combination of four critical elements:

Structured Specifications — Clear definitions of what agents must do.

Domain Expertise — The "knowledge engine" that guides reasoning and decision-making.

Engineering Architecture — The infrastructure that ensures reliability and scalability.

Human Oversight — The feedback loops that maintain accountability and governance.

Together, these elements enable the creation of agent systems that organizations can trust, deploy, and scale.

Digital FTEs are not only a technical construct; they are an economic one. They allow AI-Native organizations to package expertise, reduce execution bottlenecks, improve consistency, and create new service models, internal capabilities, and revenue streams. Built well, they do not merely automate tasks. They become scalable assets.

Why This Book Exists

Most organizations today, anywhere in the world, approach AI through isolated experiments: a prototype here, a chatbot there, a promising workflow demo that never quite makes it into daily operations.

What is missing is not excitement. What is missing is method.

Very few organizations have developed a repeatable way to build reliable AI agents that can function as a real part of the workforce. They may have access to strong models, talented people, and business demand, yet still lack the design discipline required to convert those ingredients into dependable digital workers.

This book introduces that method.

It explains how to identify valuable AI employee opportunities, turn expert knowledge into structured specifications, design bounded agent workflows, deploy them on reliable cloud-native infrastructure, and govern them with human oversight. In other words, this book teaches you to operate an Agentic Engineer: the spec-driven (you write a clear specification of the work first, then have the AI build to it), human-supervised, agent-tool-powered process by which Digital FTEs (also called AI Workers) are designed, manufactured, and deployed inside an AI-Native Company. We demonstrate this process using two tools that embody it: Claude Code , Anthropic's frontier coding agent, and OpenCode , the open-source, model-agnostic alternative. Skills, specifications, and architectural patterns written for one work in the other. The method is the constant. The tool is the variable.

By the end of this book, you will not simply understand agentic AI as an idea. You will understand how to manufacture dependable Digital FTEs as an organizational capability. These organizations will be AI-Native by default.

Find Your Path

Everyone climbs the same short ladder, and you can stop at any rung.

Foundations — start here. A handful of short courses, all in a web browser (ChatGPT, Claude, or Gemini — nothing to install). The skills everyone needs first. A doctor, an accountant, a student, and an engineer all take the same ones.
Mode 1 — use AI to do your own work faster. With the basics in hand, you put AI to work on your real tasks: writing, analysis, planning, code. You stay the doer; the AI is your power tool. Most people get enormous value and stop here.
Mode 2 — build

Two_Modes_of_General_Agent_Use

AI Workers that do the work for you. Going further, you use AI to build the tireless coworkers from the opening above — Workers that keep doing a job after you close the laptop. Now you are the builder, not just the doer.

Mode 1 uses a general agent to solve a problem inside the session. Mode 2 uses a general agent to help manufacture a custom AI Worker that can keep running after the session ends.

You don't have to climb the whole ladder — Foundations plus Mode 1 is a serious skill set on its own. Getting Started walks you up it, course by course.

New to all this? Watch the short orientation first. It gives you the core idea in a few minutes, and once that clicks, every chapter that follows becomes easier to read.

Open Full Slideshow

View Full Presentation — Agentic Engineer Orientation

Then read the Thesis for the vocabulary the rest of the book is built on — Digital FTE, AI-Native Company, the Two-Layer Model, the 10-80-10 Rule. From there, Getting Started: Crash Courses lays out the full path: Foundations first (a good entry point is AI Prompting in 2026 ), then your mode, then the courses that match it. After that, start building and reach for the Deep Dive Chapters on demand — the canonical source you open when the work itself surfaces a question. It is the same 10-80-10 rhythm the book teaches, applied to learning the book: the thesis sets the intent, the courses carry the execution, and your professional judgment closes the loop.

Who This Book Is For

This book is written for the cross-functional teams building the Agentic Enterprise . These groups often speak different professional languages, chase different priorities, and measure success in different ways — a meeting-room comedy with no laugh track. But Digital FTEs can only be built well when they work together, and this book gives them a shared framework. All of them are participating in the same larger project.

Reader Type Role in the Agentic Enterprise What You Will Gain AI Developers & Engineers Build infrastructure and systems Architectural patterns, spec-driven development, and cloud-native deployment. Domain Experts & Professionals Provide knowledge to guide behavior Methods for converting expertise into reusable AI skills and Digital FTEs that power AI-Native Companies. Enterprise Executives Lead organizational adoption Governance models, risk controls, and deployment strategies for enterprise AI. Product Managers & Architects Translate business needs into systems Frameworks for decomposing workflows into skills and verifiable outputs. Department Leaders & Operators Apply AI to operational processes Techniques for turning internal playbooks into scalable Digital FTE workflows.

AI Developers, Software Engineers & Platform Architects

The Builders

Developers and architects are responsible for turning the promise of agentic AI into production-grade systems. While many AI applications remain fragile prototypes, this book introduces a systematic engineering approach to:

Design agents using spec-driven development.

Build scalable systems with cloud-native architectures (Docker, Kubernetes, Dapr).

Implement secure and auditable tool interfaces.

Structure reusable skill libraries that encapsulate domain expertise.

Subject Matter Experts & Domain Professionals

The Knowledge Holders

The most valuable AI systems depend on deep domain knowledge. Professionals in accounting, law, finance, and supply chain possess judgment that serves as the guiding structure for AI behavior. You will learn to encode expertise into structured artifacts — specifically SKILL.md specifications (a SKILL.md is a plain-text file that packages a skill an AI can load and follow) — ensuring that:

AI executes routine reasoning, while professionals provide judgment, oversight, and accountability.

Enterprise Executives & Technology Leaders

The Decision Makers

Senior leaders must move from isolated experimentation to reliable enterprise deployment. This book provides a strategic roadmap for:

Establishing governance models and risk controls.

Implementing human-in-the-loop supervision.

Executing phased adoption from pilot programs to enterprise-wide scale.

AI Product Managers & Solutions Architects

The Translators

You play a critical role in decomposing complex business processes into automated tasks. This book offers practical guidance for:

Mapping workflows into agent skills.

Defining boundaries between automated reasoning and human decision-making.

Designing verifiable outputs and evaluation processes.

Department Leaders & Operational Teams

The Operators

Department leaders often manage workflows that are highly structured but time-intensive. This book shows how to transform internal playbooks into repeatable agent workflows to:

Reduce repetitive analytical work and improve consistency.

Extend expertise across the entire organization.

Build digital capabilities that operate continuously.

How It's Delivered: One Source, Four Channels

Most books are a destination. This one is a source. There is a single canonical source — the authoritative knowledge base that defines what agents are, how they are built, and how they are governed — and it reaches readers through four delivery channels. The methodology is the constant; the channel is the variable. When the source is updated — a new escalation protocol, a refined pattern, a sharper definition — every channel updates with it. The model that powers it can change, the app the AI works inside (its harness ) can change, the languages it is translated into will keep growing; the source remains.

Channel 01

📘 The Book

The canonical source. The authoritative knowledge base every other channel reads from.

Channel 02

💬 Zia AI

The canonical source teaching itself as a named teacher, on the learner's own free Claude. One connector, authorize once — no install, no cost to serve.

Channel 03

🛠️ Agentic Engineer Plugin

The canonical source installed into the developer's coding agent — Claude Code or OpenCode — as a plugin that picks the right architecture for the job and builds to it.

Channel 04

📚 Derivative Books

The canonical source rewritten for every audience and every domain — by topic, age, and profession.

These four channels reach everywhere the work is being done. The derivative books travel across languages, age groups, and professional disciplines. Agentic Engineer Plugin installs into the coding agents already in the hands of millions of developers — Claude Code and OpenCode. Zia AI meets learners on the surface where everyday AI value already lives — the chat tab — running on each learner's own free Claude, so it scales to anyone, anywhere, at no cost to serve.

Three Modes of Delivery

Most books are written to be read. This book is written to be read, to teach through an AI tutor, and to guide an AI building partner — all from the same knowledge base. It is the foundation of a learning and development ecosystem designed for three modes of delivery.

📖

Mode 1 · Read

Human Reading

The traditional path. Read the chapters, study the frameworks, complete the exercises, and build deployable artifacts. Each chapter is a self-contained unit of professional education — and the family of derivative books extends this mode across topics and audiences.

💬

Mode 2 · Tutor

Zia AI

Your personal AI teacher — a named, real-teacher twin, not a faceless system. Built as a connector-native app: add one connector to your free Claude, authorize once, and Zia AI greets you by name, recalls where you left off, teaches in Zia's own method and voice, checks understanding, and records your progress — with persistent memory across chats, on a surface every learner can already reach for free.

The book gives Zia AI its expertise. Zia AI gives the book a teacher.

🛠️

Mode 3 · Build

Agentic Engineer Plugin

Your AI building partner, installed as a plugin into Claude Code or OpenCode . You describe your business requirements and domain; the plugin decides the right architecture for the job — Mode 1 Problem-Solving or Mode 2 Manufacturing — and builds to it. For Mode 1 it writes the prompt. For Mode 2 it recommends and scaffolds the right shape: a connector-native app, a plugin, or an AI Worker (OpenAI Agents SDK or Claude managed agents). When the requirements aren't enough to decide, it asks.

Where Zia AI teaches the method, Agentic Engineer Plugin walks beside you during construction.

Two of these modes are the same architectural move aimed at two different hosts: Zia AI is a connector-native app that extends the chat app (claude.ai) for learners; Agentic Engineer Plugin extends the coding agent (Claude Code, OpenCode) for builders. The ecosystem teaches both patterns — and runs on them.

Why this matters. The same knowledge base powers all three modes. When a chapter is updated — a new jurisdiction overlay for banking compliance, a refined escalation protocol for legal ops — the update propagates to Zia AI's teaching and Agentic Engineer Plugin's guidance simultaneously. The book is not a static artifact. It is the single source of truth for an ecosystem: human learning, AI tutoring, and AI-assisted building, all drawing from one authoritative foundation.

This is the 10-80-10 pattern applied to education itself. The book sets the intent (the first 10% — the domain knowledge, the frameworks, the professional standards). Zia AI and Agentic Engineer Plugin handle execution (the 80% — the personalized teaching, the step-by-step building guidance). You verify the outcome (the final 10% — the professional judgment that confirms the agent is correct, the deployment is safe, and the knowledge is sound).

Two Tools, One Discipline

Claude Code and OpenCode are not competitors in this book. They are two expressions of the same discipline.

Why two tools, not one? Because the discipline this book teaches must outlive any specific tool. Agentic Engineer method — spec-driven design, skill-based architecture, human oversight — is portable by construction. Binding it to a single vendor's product would contradict the very premise of the method. It would also inherit risks readers cannot control: pricing changes, access restrictions, strategic shifts. And it would silently exclude readers whose constraints — economic, regulatory, or architectural — make the dominant tool inaccessible.

Two tools, one discipline. Not a compromise — the design. Skills, specifications, and architectural patterns written for one work in the other. The method is the constant. The tool is the variable.

Claude Code

Frontier-first

Anthropic's frontier coding agent. Runs Anthropic's most capable models, ships with a polished developer experience, and offers the deepest integration with the Claude ecosystem.

Best for: complex multi-file refactors, production-critical work, and reference implementations where frontier model performance is the constraint.

OpenCode

Open & model-agnostic

The open-source alternative. Connects to dozens of model providers — Claude, GPT, Gemini, DeepSeek, Qwen, local models via Ollama — and lets you switch between them as economics, latency, and task complexity demand.

Best for: daily coursework, learning, experimentation, and any context where flexibility, cost control, or vendor independence matters.

Both implement the same patterns this book teaches. Skills, subagents, hooks, MCP servers (MCP is the standard way an agent plugs into outside tools and data), and the spec-driven workflow work identically in both. A SKILL.md written for Claude Code drops into .opencode/skills/ and runs unchanged. The discipline is portable.

A System of Record for the Agent Era

Jensen Huang, CEO of NVIDIA, has argued that AI agents do not eliminate the need for systems of record — the single trusted sources of truth a business reads from, writes to, and verifies against — they reinforce it. Agents need ground truth. They need authoritative places to read from, write to, and verify against. Without that foundation, agents hallucinate. With it, they execute.

Huang is solving this for the enterprise. The databases, workflows, and operational platforms that companies have spent decades building become more essential in the agent era, not less. Agents do not replace SAP or ServiceNow. They use them — at machine scale.

But there is a layer Huang is not solving for: the human layer.

Millions of developers, architects, and domain professionals are about to build AI agents. Most of them have no canonical source to learn from. No structured body of knowledge that has been designed for verification, not just consumption. They are learning from scattered tutorials, outdated blog posts, and model outputs that may or may not reflect how production agent systems actually work.

And when those same developers move from learning to building, they face the same problem in a different form. Their AI coding partners draw on whatever the model happens to surface — patterns that may never have been verified, bounded, or designed to produce dependable Digital FTEs. Without a verified source, both human learning and AI-assisted building inherit the same fragility.

Agentic Engineer Book is a system of record for agentic AI education and construction

One source, many derivative books — specialized by topic and audience

The system of record pattern, as it applies to AI education: Zia AI is the bounded agent, the book is the canonical source, and human judgment verifies what is taught.

This is not a metaphor. The book's architecture follows the same pattern Huang describes for enterprise systems:

The book is the canonical source of truth — the authoritative knowledge base that defines what agents are, how they are built, and how they are governed.

Zia AI is the teaching agent — it reads from the book, not the open internet, and teaches from verified knowledge rather than probabilistic generation.

Claude Code and OpenCode are the building agents — equipped with Agentic Engineer Plugin, they read from the book rather than Stack Overflow or scattered tutorials, and construct Digital FTEs and AI-Native Companies from verified specifications, SKILL.md templates, and architectural patterns rather than improvised code.

Human judgment is the verification layer — students, instructors, developers, and domain experts confirm that what Zia AI teaches and what the Plugin-equipped coding agent builds matches the book's intent. This is the final 10% of the 10-80-10 pattern.

But education was only

The system of record pattern, applied to both AI education and construction

half the story. The same pattern extends to construction — and once you draw both pipelines side by side, the symmetry becomes the architecture itself.

The full pattern: Zia AI teaches from the book, Agentic Engineer Plugin directs Claude Code and OpenCode as they build from the book, and human verification flows back to improve the source — the same canonical knowledge base powering both lanes.

But the pattern does not stop at education and construction. The same source feeds a third lane: a growing family of derivative books, each specialized along one of two axes — topic or audience — yet inheriting the same vocabulary, architecture, and standards from the source.

The publishing layer of the system of record: the canonical Agentic Engineer book branches into derivative editions specialized by topic and by audience. The methodology is the constant; the topic and the audience are the variables.

The topic axis. Some derivatives narrow the scope to a single discipline that the Agent era is reshaping. Learning Python in the AI Era teaches Python the way it now needs to be taught — alongside agentic coding tools, spec-driven workflows, and the SKILL.md format that runs in Claude Code and OpenCode. Critical Thinking in the AI Era equips readers with the judgment skills required when AI workers handle the routine reasoning. Learning Agentic Primitives compresses the foundational concepts — agents, skills, subagents, hooks, MCP, oversight loops — into a focused primer. More titles will follow as the methodology matures.

The audience axis. Other derivatives keep the methodology constant but rewrite it for the reader. Editions for primary, secondary, and high-school students introduce age-appropriate framings of the same architectural ideas — so a high-school student can build their first SKILL.md using the same vocabulary their professional counterpart will use a decade later. Profession-specific editions adapt the material for engineers, doctors, architects, lawyers, accountants, bankers, and other domains where the workforce is being redrawn around Digital FTEs. The framework is constant. The examples, the priors, and the depth shift to meet the reader where they are.

When the canonical methodology is updated — a new escalation protocol, a refined Plugin pattern, a sharper definition — the update propagates through the entire family. Every derivative inherits the correction.

And there is a deeper symmetry at work. This book does not merely use a system of record — it teaches you how to build agents that use systems of record, and it powers the very building agents (Claude Code and OpenCode, equipped with Agentic Engineer Plugin) that help you construct them. The architecture of the learning system, the architecture of the construction system, and the content of the curriculum all mirror each other. You learn the pattern by experiencing it. You build the pattern by using it.

Huang solved verification for the enterprise. This book solves it for the people who will build those enterprises.

The same principle runs one layer down, in the infrastructure: the Digital FTEs you build need a literal system of record too — and the book's stance there is the same, consolidate by default, specialize deliberately , with one Postgres holding relational data, documents, full-text search, and AI vectors together rather than scattered across systems that drift out of sync. (See the Thesis for the architecture, and Give Your AI Searchable Context for the build.)

Two Ways to Read It: Crash Courses and Deep Dive Chapters

The book content comes in two reader-facing tiers, and you move between them freely.

Getting Started: Crash Courses are short, high-leverage primers — the fast path that covers roughly the 80% of agentic work you reach for daily. They get you productive in hours, not semesters, and they are where most readers begin.

Deep Dive Chapters are the comprehensive book: the full treatment of every concept, organized into parts and chapters. You do not read them front to back. They are the reference you return to whenever real work surfaces a gap — a spec, a SKILL.md, an MCP connector, an escalation rule, a governance question.

The crash courses get you working; the chapters keep you working.

Building the Agentic Enterprise

Agentic AI is not a feature. It is a workforce. The next generation of companies will be built around it the way the last generation was built around software — and the discipline by which that workforce is designed, manufactured, deployed, and governed will decide who wins the next decade.

That contest is global by definition. It will not be won by whoever has the largest model or the deepest GPU stack; it will be won by whoever can turn AI capability into reliable, governable, repeatable execution at the workforce layer. The teams that win it will not all sit in the same handful of cities. They will sit anywhere ambitious people with internet access and a working knowledge of agentic engineering decide to build.

There is a pattern in how AI tools have evolved, and it points to where the lasting value sits. The first era of AI tools made the model the product. The second era made the harness the product — Claude Code, OpenCode, Cursor, the agentic coding environments where models do their work. Some are now positioning the harness platform — the SDKs, the plugins, the vendor-specific extension layers — as the third era. We sit one layer above that. The third era we mean is the era in which the discipline that runs across harnesses and across their platforms becomes the product. The model commoditizes. The harness commoditizes. The harness platform commoditizes. What survives all three is the canonical source: the methodology, the vocabulary, the verification standards, and the SKILL.md library that any harness honoring the format can load and run.

Why does that discipline suddenly matter so much? Because of where the economics are heading.

"We're going to see ten-person billion-dollar companies pretty soon — billion-dollar valuations. In my little group chat with my tech CEO friends, there's this betting pool for the first year that there is a one-person billion-dollar company — which would have been unimaginable without AI — and now it will happen."

— Sam Altman , OpenAI, in conversation with Alexis Ohanian, January 2024 ( video · analysis )

Anthropic CEO Dario Amodei has since narrowed the timeline, giving the first single-person billion-dollar company a strong majority chance of arriving soon — and naming developer tools, automated customer service, and proprietary trading as the most likely categories. Within months, the first concrete example appeared: a solo founder built a telehealth business to hundreds of millions in first-year revenue, using rented infrastructure and AI agents in place of employees. More examples are arriving every quarter.

The architectural shape they build is the same one Altman and Amodei describe: a canonical source the founder owns, AI agents executing the work that historically required teams, and rented infrastructure — harnesses, messaging platforms, model providers — carrying the rest. Agentic Engineer ecosystem is itself one example of that shape. The book is the source of truth. Zia AI teaches and Agentic Engineer Plugin builds — the work that would normally take a team. Everything else — the chat apps, the coding tools, the AI models themselves — is rented from other companies rather than built from scratch. The book teaches readers to build companies of this shape. The ecosystem they are reading from is one.

The reader who finishes this book understands more than agentic AI as an idea. They understand how to identify the work that becomes a Digital FTE, how to specify the agent that performs it, how to deploy the architecture that runs it, and how to govern the workforce that emerges from it.

The goal is simple: move beyond AI curiosity and into AI execution. Expertise becomes operational. Workflows become repeatable. Capabilities become products. Organizations gain a new kind of workforce — digital, dependable, and built by design — and the people who learn to build that workforce gain leverage no previous generation of knowledge worker has had.

Agentic Engineer ecosystem exists to put that leverage in their hands.

Start Building With the Ecosystem

One canonical source, four delivery channels. Read the book, talk to the tutor, equip your build agent — pick the entry that fits how you learn and ship.

Read the Thesis Agentic Coding Crash Course AI Worker Catalog

Preface: Why now, what's at stake