How to Use This Book

This book is written for four kinds of reader, and no reader needs all of it. Find your route in this chapter, read what it asks, and skip the rest until you need it. The book is long, but your route is not. The shortest route takes 5 to 8 hours of reading.

Start here today. Choose your route below. Then read Part I, and pick one area of your own work. Apply every exercise to that area. If you do not have one yet, use Brightline's AP Worker, the book's running example. It is an accounts payable (AP) worker for a small U.S. business.

Four reader routes

Choose the route that matches your work today. You can change routes later. PCxx exams are Panaversity's certifications, and CCxx exams are Anthropic's. PCAO-F is the Associate exam, PCAR-F the Architect Foundations exam, PCDV-F the Developer exam and PCAR-P the Architect Professional exam.

Reading time assumes 120 to 200 words a minute, because study reading is slower than everyday reading. It uses the measured length of the parts already published, and estimates for the rest. The domain-expert time is an older estimate, and it will be updated as Parts III to V are written. Exercises and builds take extra time.

Figure F2.1. Which parts each route reads.

The builder route is the longest. It takes 15 to 26 hours of reading, plus the time to build. Parts III to V are not written yet, so this figure may grow. The Developer companion, a later release, adds 2 to 3.5 hours more. That is a real commitment, so plan for it.

On the builder route, Chapter 12 teaches you to drive a coding agent. Chapters 13 to 15 cover programming fundamentals, program structure and code review. Each idea comes first with no language, then in TypeScript, the language of the running project, and in Python. From Chapter 16, you build with that agent: skills and plugins first, then connectors.

On every route except the leader route, your first credential is a Panaversity PCxx exam. The Anthropic certifications come later, and the roadmaps show how readers reach them, with each exam and portfolio milestone in order.

A few notes on choosing:

• Not sure which route? Start with the everyday professional route. Its reading, Parts I and II, is part of every other route except the leader route, so none of it is lost if you switch.
• New to AI? Read Part 0, How AI Works, before Part I. It takes about 6 hours, with its four labs. Part 0 is optional: if you can already explain why AI sometimes sounds right and is wrong, go straight to Part I.
• An accountant, lawyer or other specialist? Take the everyday professional route if you want AI Workers to help with your own work. Take the domain-expert route if you want to build one for others in your field, together with a builder.
• A founder with a technical partner? Take the domain-expert route and read it beside your partner's builder route. Chapter 46 explains how the founding pair divides the work.
• Leading a company or a ministry? You do not need to build. You do need Part I, because the vocabulary of every later conversation starts there.

What you need. The builder route builds software with a coding agent. On the other routes, you work with everyday AI products.

You can start the exercises and labs on the free plans of Claude¹ and ChatGPT.² Both plans were checked on 2 October 2026, and plans change often. Some later exercises need a paid subscription, and builders pay separately for API usage on both Anthropic's³ and OpenAI's⁴ platforms. Each chapter's dated section on current tools says which plans its exercises need, and we review those sections every month. The open-source tools are free to use. Running them takes your own computer or server, and an account with a model provider unless you run a model yourself.

Three journeys, one path

The book connects three journeys. Every reader develops capability. Certification and economic goals depend on the route you choose. An exam guide teaches certification. A skills book teaches capability. A career book talks about income. This book keeps all three on one path, so you can follow as many as your route needs. The economic journey starts with better work in your current role, and it can grow into a service, a business or national capacity.

A certificate without capability does not survive a client's first real task. A credential helps a client in another country trust your capability, alongside your portfolio and your results. Neither one makes money until it becomes a service, a product or a role. That is why the book teaches them together.

The "You are here" panel

Every part opens with a short panel that shows your position on all three journeys. It fits on one screen. Here is the panel that opens Part I:

Every panel has the same rows, so you learn to read it once. Read the panel before each part. If you are lost later, go back to it.

If you are a domain expert

If you are an accountant, lawyer, doctor or engineer on the domain-expert route, you still read the technical parts. You read each one at the depth its chapter asks of you. An AI Worker in your field is only as good as the judgment you put into it. So every chapter in Parts III to V carries one of four statuses for you.

Manager chapters open with a summary for you. It is about 500 words long. It covers what the concept does and the questions to ask a builder about it. Read the summary instead of the full chapter.

Co-build chapters are where your expertise enters the system. The running project in this book is an accounts payable (AP) worker for a small U.S. business. At each co-build step, you will see what the AP expert supplies beside what the builder implements. For example, the AP expert supplies approval thresholds, exception cases and sign-off criteria. Your version of that step uses your own field.

Two vendors, open source, one set of principles

The book teaches two AI vendors, Anthropic and OpenAI, and the main open-source tools beside them. In the authors' judgment, Anthropic and OpenAI lead in models and harnesses, the software that lets a model use tools and carry out work in steps. That is an editorial position, reviewed every year, and not a permanent fact. Teaching the two leaders keeps the book current.

Open source is the third option. The book uses three open-source projects:

• OpenCode, a coding agent that runs on your own computer.⁵
• OpenClaw, an assistant that keeps working while you are away.⁶
• Omnara, a runtime for running AI Workers on your own servers.⁷

With these tools, you choose the AI model, including one that runs on your own computer. You also keep the worker on computers you control. They are the only route when a client's data must never leave its own systems, even for the model. But they move the security work to you. Every chapter that shows an open-source tool also says how to run it safely.

Each principle is stated without vendor or project names, and it must stay true on all three. That keeps the principles neutral.

Other commercial model vendors are not taught or compared. Other companies appear only as systems a worker connects to, such as a messaging app or a client's accounting system. There is one exception, for an exam. CCDV-F expects awareness of third-party agent frameworks,⁸ so Chapter 21 carries a short exam note. The Anthropic exams cover Claude only, so open-source tools are never examined there. Chapters that show them say so in their exam notes.

Every technical topic follows the same seven steps:

1. Principle: the concept, with no vendor or project names.
2. Anthropic: how Claude's products do it, in a dated box.
3. OpenAI: how OpenAI's products do it, in a dated box.
4. Open source: how the main open-source tools do it, in a dated box, with notes on running them safely. Where open source has no fair match, the box says so.
5. Comparison: only the differences that change an architecture decision. There is no winner, and the book does not pretend the three are equal where they are not.
6. Invariant: what stays true if any runtime is replaced.
7. Lab: a portable specification, built on one vendor, with a porting exercise to another vendor or to open source where it teaches something.

Figure F2.2. The teaching pattern: two vendors and open source.

Read the principle and the invariant as the lasting part of each topic. Read the dated boxes as a snapshot. Products and projects change every month. Principles change far more slowly.

The layers you own are designed so that they never depend on any vendor or tool. These layers are KSoR, DSoR, SSoR, the Role Contract, the Authority Envelope, 10-80-10, review contracts and evaluations. The platforms are rented. The knowledge and the controls are yours.

Companions and field guides

The book teaches principles, with exercises and labs to practice them. Today's product detail is in each chapter's dated section on current tools. Most exam depth, exact procedures and extra practice live outside the book. That split keeps the book short enough to finish, while detailed exam preparation and implementation guidance stay available. One rule protects you: a companion may deepen a principle, but the book never depends on a companion to state one.

The four companions are Associate, Architect Foundations, Developer and Architect Professional. The first two arrive with the book. The Developer and Architect Professional companions and the country workbook follow in a later release. Inside the book, Appendix C prepares you for CCAO-F: it shows where each exam objective is taught, and has a timed sample exam.

Each chapter's dated section on current tools, each field guide and each product-dependent companion page shows the date it was last verified. Check that date. If it is old, the product may have changed since. Those sections and the field guides are reviewed every month, and screencasts are re-recorded when their field guide changes.

Learning with Zia Tutor AI

Reading a concept is not the same as owning it. Zia Tutor AI closes that gap. It teaches one numbered concept at a time and checks that you have it before you move on. It is served from the same approved source as this book, so it teaches the same version of each concept. If the tutor and the book ever disagree, the book is the authority.

To use the tutor, add the Zia Tutor AI connector to your AI assistant. The book's website gives the current setup steps.

A session with the tutor follows a fixed rhythm:

1. What happens: a situation first, then the term that names it.
2. Why it works that way: the reason behind the behavior.
3. What it rules out: the wrong picture, named as wrong.
4. Say it back: you explain the concept in one line, in your own words.
5. Check: about four multiple-choice questions. The concept closes when you answer them with at most one miss.

Every teaching reply ends on a question you could get wrong. That is deliberate. A question you cannot get wrong teaches nothing.

If you cannot use the tutor, follow the same rhythm on your own. Read the numbered concept, explain it in one line in your own words, then answer its practice questions and build its artifact.

Work through each concept with the tutor after you read its chapter, and return to it for review before an exam.

The tutor checks understanding. It does not replace the labs. Capability comes from producing the artifact.