THE ARCHITECTURE OF INTEGRITY

This is a book about a strange kind of law. Unlike most criminal statutes, which tell you what not to do, the anti-corruption frameworks built over the last five decades tell companies what to build. They describe codes of conduct, whistleblower channels, due-diligence procedures, training programs, risk maps, internal investigations. They reward companies not for being innocent — corruption, after all, is usually committed by an individual, a manager, an agent acting in the company's interest — but for having tried, systematically and demonstrably, to prevent it.That shift, from punishing acts to evaluating systems, is the quiet revolution this book tries to describe. It did not happen all at once, and it did not happen in one country. It began in the United States in 1977, spread unevenly through the 1990s and 2000s via an OECD convention that dragged reluctant exporting nations along, accelerated sharply after 2010 in Britain, found its most severe institutional expression in France after 2016, arrived in Brazil in the wake of the largest bribery scandal in the hemisphere's history, and reached Argentina only in 2018 — a full forty-one years after the FCPA, and still one of the newest members of this club of nations that hold companies, not just individuals, criminally accountable for corruption.Each of these laws is usually taught in isolation — a course on the FCPA here, a seminar on the UK Bribery Act there, a CLE credit on Ley 27.401 for practitioners in Buenos Aires. This book takes the opposite approach. It reads them together, as chapters in a single, still-unfinished argument about how the modern corporation should be governed. The case studies that anchor each chapter — Airbus, Odebrecht, Rolls-Royce, Goldman Sachs, Skanska — are not included as legal trivia. They are the moments where the abstract architecture of a statute met the concrete reality of a company, and the outcome of that meeting is the most honest evidence available of what each law actually demands.The book closes with what I consider the more useful half of the exercise: not just knowing that these frameworks exist, but knowing what to build. If Part One is a comparative history, Part Two — the final chapters — is a practitioner's argument about architecture: what an integrity program actually needs to contain, how to measure its maturity honestly, and where this entire field is likely headed next.