In this section: Chapters
- Part 0: Monday Morning
- Introduction
- Part I: The Problem
- Ch.1: The Day After
- Ch.2: Tribal Knowledge Is the Bottleneck
- Part II: The Architecture
- Ch.3: Contracts Are the Answer
- Ch.4: Capability Graphs, the New Atomic Unit
- Ch.5: Extraction Over Refactoring
- Ch.6: Making Your System Legible to AI Agents
- Part III: The Transformation
- Ch.7: The Architect
- Ch.8: The Developer
- Ch.9: The PM / PO
- Ch.10: The Designer
- Ch.11: Leadership
- Ch.12: The Company That Gets There First
- Appendices
- Appendix A: The C-DAD Specification
- Appendix B: MCP Documentation and Implementation Resources
- Appendix C: The Agent Onboarding Test
- Appendix D: The Interaction Contract Template
Appendix A: The C-DAD Specification
Contract-Driven AI Development, C-DAD, is the framework I set out in a white paper. Its premise is that contracts, not code, should be the surface on which humans, AI agents, and runtimes collaborate.
The white paper, not this site, is the place for the twenty-one principles, the contract lifecycle, and the adoption playbook.
Forthcoming from Apress. ISBN 9798868834516.