anchor.diff:  
   The in-process Executor creates a Garden container in the Diego cell. Garden downloads the droplet that resulted from the staging process and runs the app in the container. 
   
  -![An arrow points from a box labeled "executor" to an unlabeled box inside of a box labeled "garden". This indicates that the executor sub-process of the rep process on the diego-cell VM communicates to the garden process on the diego-cell VM to create a new container. Another arrow points from the box labeled "garden" to a cylinder labeled "droplets" to indicate that the garden process also communicates with the droplets bucket on the singleton-blobstore VM to download the droplet.](../images/oss-diego-architecture-4.png)
  +![An arrow points from a box labeled "executor" to an unlabeled box inside of a box labeled "garden". This indicates that the executor sub-process of the rep process on the diego-cell VM communicates to the garden process on the diego-cell VM to create a new container. Another arrow points from "garden" to a cylinder labeled "droplets" to indicate that the garden process also communicates with the droplets bucket on the singleton-blobstore VM to download the droplet.](../images/oss-diego-architecture-4.png)
   [//]: https://docs.google.com/drawings/d/1IPLl2bKmR9iYOhjXvlRZJSvCeCnoaX_zqARdt04Yjv4/edit?usp=sharing
   
   ###<a id='step-5'></a> Emits Route for App
  
positive.code: 
  The Cloud Controller passes requests to run apps to the Diego BBS, which stores information about the request in its database. 
  
  ![An arrow points from a box labeled "cloud_controller_ng" to a box labeled "bbs" to indicate that the cloud_controller_ng process is sending a request to run an app to the bbs process. Another arrow points from the box labeled "bbs" to a  cylinder labeled "bbs db" to indicate that the request gets stored in a database.](../images/oss-diego-architecture-1.png)
  [//]: https://docs.google.com/drawings/d/1p2ShJ8yJ3gVzKBh1sw1b_O8qMASXMzC37r2MU3L4xmI/edit?usp=sharing
  
  ###<a id='step-2'></a> Passes Request to the Auctioneer Process
  
negative.code: 
  The Loggregator agent forwards app logs, errors, and metrics to the Cloud Foundry Loggregator. For more information, see the [Application Logging in Cloud Foundry](../../devguide/deploy-apps/streaming-logs.html) topic.
  
  ![An arrow from an unlabeled box inside a box labeled "garden" points to a box labeled "loggregator-agent". This indicates that the container running the app inside the garden process of the diego-cell VM emits logs to the loggregator-agent process of the diego-cell VM. An arrow from "loggregator-agent" points to a box labeled "doppler", and from "doppler" to a box labeled "traffic-controller" to indicate the where logs are sent.](../images/oss-diego-architecture-6.png)
  [//]: https://docs.google.com/drawings/d/1ChpsoNXR-zHC2n9bPz2H5qdRvkDfg_M4I8sVr-Vy3So/edit?usp=sharing
  
  ## <a id='components'></a> Diego Components
  