184 posts
EN ES
Governing Rust by Contract cover

Governing Rust by Contract

Owning the bits, from the compiler to the cluster. GDCD in Code, Book 1.

115 pages · 13 chapters · PDF + web

Book 1 of the GDCD in Code series. Why an enterprise architect chooses Rust, and how to govern it with contracts. The book separates what the compiler really proves, what tooling must enforce around it, and what people and operations still own: the decision record and its renewal, when not to use Rust, unsafe and FFI as signed exceptions, verification, the toolchain and dependency pins, the admission gate for the supply chain, the public API promise, shipping binaries and images, and running on Kubernetes. It includes templates and a small reference service you can rebuild and measure.

What's inside

  1. Why This Book
  2. Own the Bits: What Rust Changes and What It Does Not
  3. The Decision Record and Its Renewal
  4. When Not to Use Rust
  5. The Compiler Contract
  6. The Exception Contract: Unsafe, FFI and Build-Time Code
  7. The Verification Contract
  8. The Pin: Dependencies and Toolchain
  9. The Admission Gate
  10. The Interface Promise
  11. Shipping the Artifact
  12. Running Under Contract
  13. The Operating Model
  14. Appendix A: Templates and the Reference Service
  15. Appendix B: The Three Tiers in Other Languages
  16. Appendix C: Glossary and Source Register

Read the companion essay to this guide: on the blog ›