anchor.diff:  If the platform skips detection, it performs the following interactions:
   
   1. For each buildpack except the last buildpack, the platform does the following:
  -	1. Creates a `/tmp/deps/IDX/` directory
  -	1. Creates a `/tmp/cache/MD5/` directory
  -	1. Runs `/bin/supply /tmp/app/ /tmp/cache/MD5/ /tmp/deps/IDX`
  -	1. Accepts any modification of `/tmp/deps/IDX/`
  -	1. Accepts any modification of `/tmp/cache/MD5/`
  +	1. Runs `/bin/supply` on the `app`, `cache`, and `deps` directory
  +	1. Accepts any modification of the `deps` directory
  +	1. Accepts any modification of the `cache` directory
   	1. May disallow modification to any other directory
   1. For the last buildpack, the platform does the following:
  -	1. Creates `/tmp/cache/primary/` if not present
   	1. If `/bin/finalize` is present:
  -		1. Creates `/tmp/deps/` if not present
  -		1. If `/bin/supply` is present, runs `/bin/supply /tmp/app/ /tmp/cache/primary/ /tmp/deps/ IDX`
  -		1. Accepts any modification of `/tmp/deps/IDX/`
  -		1. May disallow modification of `/tmp/app/`
  -		1. Runs `/bin/finalize /tmp/app/ /tmp/cache/primary/ /tmp/deps/ IDX`
  -		1. Accepts any modification of `/tmp/app/`
  +		1. Creates the `deps` directory if not present
  +		1. If `/bin/supply` is present, runs `/bin/supply` on the `app`, `cache`, and `deps` directory 
  +		1. Accepts any modification of the `deps` directory
  +		1. May disallow modification of the `app` directory
  +		1. Runs `/bin/finalize` on the `app`, `cache`, and `deps` directory 
  +		1. Accepts any modification of the `app` directory
   	1. If `/bin/finalize` is not present:
  -		1. Runs `/bin/compile /tmp/app/ /tmp/cache/primary/ ‘’`
  -		1. Accepts any modification of `/tmp/app/`
  +		1. Runs `/bin/compile` on the `app` and `cache` directory 
  +		1. Accepts any modification of the `app` directory
   	1. Runs `/bin/release` to determine staging information
   
  -At the conclusion of this process, `/tmp/deps/` is included at the root of the doplet, adjacent to `/tmp/app/`.
  +At the conclusion of this process, the `deps` directory is included at the root of the droplet, adjacent to the `app` directory. 
   
   ###<a id='detection'></a> Buildpack Detection
   
  
positive.code: ```
  The `app` directory contains `BUILD_DIR` contents, and `staging_info.yml` contains the staging metadata saved in the droplet.
  
  ##<a id='buildpack-detection'></a> Buildpack Detection
  
  When you push an app, Cloud Foundry uses a detection process to determine which buildpack to use. 
  
negative.code: 
  This section provides a detailed account of the sequence of interactions between the Cloud Foundry platform and the buildpack. The sequence of interactions differs depending on whether the platform [skips](#no-detection) or [performs](#detection) buildpack detection.
  
  ###<a id='no-detection'></a> No Buildpack Detection
  
  The platform skips buildpack detection if the developer specifies one or more buildpacks in the application manifest or with the cf CLI using the `cf push APP-NAME -b BUILDPACK-NAME` command.
  