Merge pull request #50 from Minimum-CD/update-deployable

Update deployable

README.md

@@ -23,7 +23,9 @@ CD is the engineering discipline of delivering all changes in a standard way saf
 The minimum activities required for CD are:
 
 - [Continuous integration](#continuous-integration)
-- The [application pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract) is the only path to deploy to production
+- The [application
+  pipeline](https://www.informit.com/articles/article.aspx?p=1621865&seqNum=2#:~:text=%EE%94%80Buy-,What%20Is%20a%20Deployment%20Pipeline%3F,-At%20an%20abstract)
+  is the only path to deploy to production and should be [definitive for deploy](./faq.md#why-should-the-pipeline-be-definitive-for-deploy)
 - [Always meets the organization's definition of deployable](https://www.youtube.com/watch?v=bHKHdp4H-8w)
 - Immutable artifact. No human changes after commit.
 - All feature work stops when the pipeline is red

faq.md

@@ -35,4 +35,10 @@ Oh, gosh no! This is the barest of minimums.
 
 CD requires CI and CI requires Trunk-Based Development. Start at the bottom and work your way up. Ask yourself, "why
 can't we do this yet?" Solving that problem is the engine of org improvement. We have not seen a single instance where
-CD cannot apply. It just takes longer in some situations to solve the problems. It's worth it though. It improves everything.
+CD cannot apply. It just takes longer in some situations to solve the problems. It's worth it though. It improves
+everything.
+
+## Why should the pipeline be definitive for deploy?
+
+"If the pipeline says everything looks good, that should be enough - it forces the focus on what 'releasable' means." -
+Dave Farley