Skip to slide
149 / 170

CH 16 · Production Realities: Economics, Security, and Governance · 01/11

Read as one page

Production Realities: Economics, Security, and Governance

Running coding agents across an engineering org surfaces real costs, security incidents, and the limits of trusting fluent output.

11 slides · 7 min read

Contour map for Production Realities: Economics, Security, and Governance

In this chapter

  1. 01The economics (and why they surprise people)
  2. 02Where agents excel and where they struggle
  3. 03The verification principle
  4. 04The 2026 security incidents
  5. 05Governance and the staged rollout
  6. 06Why it matters
  7. 07How it works: a cost-per-task model
  8. 08Code MVP: a cost-per-task estimator
  9. 09Connecting to the bigger picture
  10. 10Key takeaways

You can build a working agent. Running it across thousands of repositories and hundreds of engineers is a different problem, and it is mostly not a capability problem. As the "Everything About Codex" guide puts it, at scale "the question is never can the agent write the code. It is can you prove what every agent touched, constrain what it can reach, and review what it ships." This chapter is about those questions: the economics that surprise teams, the security incidents that made 2026 a wake-up call, and the governance that turns a capable agent into a deployable one. It is lighter on code because the lessons are mostly judgment, but it ends with a small cost model because cost is the lesson teams underestimate most.

Finished this idea?

Your learning progress stays in this browser.