Engineering Foundations

This part has six chapters, and together they answer one question: what does it actually take, in engineering terms, to turn "a proof that runs" into "a production system worth trusting"?

This is where the line Part Two ended on gets cashed in: the acceptance contract is signed, and plenty of obstacles are still standing.

Chapter 9 opens by breaking "going to production" into eight walls, each definable and each subject to acceptance — and makes one recommendation: count the walls before you quote a price and a schedule. A quote that hasn't counted the walls is a landmine buried at the contract stage.

Then the book tackles the walls one by one: how to wire up data and permissions (Chapter 10, Walls One and Two); how to constrain what an agent can do so it's safe to put in production (Chapter 11, Walls Three and Four); how to prove results haven't regressed (Chapter 12, Wall Five); how to earn the customer's trust in the results (Chapter 13, Wall Six); how to keep the bill and the system's stability under control (Chapter 14, Wall Seven). Wall Eight — transferable responsibility — gets its full payoff in Chapter 17.

The six chapters form one chain: only once the data is wired up can an agent actually act; only once its actions are governed does it make sense to talk about proving results; only once results are provable does it make sense to talk about trust; only once results are trusted do money and stability still need holding down — loosen one link, and the whole chain goes slack.

The primary reader for this part is whoever is on the hook for production: the technical lead for delivery, the engineer leading the on-site team, the customer-side technical representative who has to sign the acceptance form. The eight walls get translated into engineering language, but every one of them starts with something a customer actually says — "the data can't leave our domain," "whose fault is it if this runs wild at 2 a.m.," "where does this number come from," "why is the bill this big." Organization and adoption are Part Four's business; pricing and the business model are Part Five's. This part answers exactly one question: what makes this system worth trusting with the job.