More detail in the philosophy section (#258)

Author: andyblundell

README.md

@@ -19,7 +19,10 @@ It aims to:
 The philosophy underpinning this framework advocates:
 * Empowered teams which are accountable for their products
 * Rapid, iterative and incremental development: "Release early. Release often. And listen to your customers." (Eric S. Raymond in [The Cathedral and the Bazaar](https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar))
-* Reliable services, remembering "Everything fails, all the time" (Werner Vogels), and treating operations as a software engineering challenge (as in Google's [Site Reliability Engineering](https://landing.google.com/sre/))
+* Robust and comprehensive automation supporting and enforcing quality 
+* Reliable & scalable services, remembering "Everything fails, all the time" (Werner Vogels), and treating operations as a software engineering challenge (as in Google's [Site Reliability Engineering](https://landing.google.com/sre/))
+* Loosely-coupled & cloud-native composable components as the default mode of construction
+* Continuous improvement, with prioritisation decisions based on data rather than sentiment
 
 ## Context