anchor.diff:  
   [**Inigo on GitHub**](https://github.com/cloudfoundry-incubator/inigo)
   
  -### Auction
  +### <a id='auction'></a>Auction
   
  -- encodes the behavioral details around the auction.
  +- encodes the behavioral details around the [auction](./diego-auction.html).
   
   - includes a simulation test suite that validates the correctness and performance of the auction algorithm.  The simulation can be run for different algorithms, at different scales.  The simulation can either be run in-process (for quick feedback loops) or across multiple processes (to understand the role of communication in the auction) or even across multiple machines in a cloud-like infrastructure (to understand the impact of latency on the auction).
   
  
positive.code: 
  Diego schedules and runs **Tasks** and **Long Running Processes**:
  
  > A **Task** is a one-off job and is guaranteed to be run at most once.
  
  > A **Long Running Process**, (LRP) such as an app, is meant to run until explicitly terminated, and may have multiple instances.  
  
  Diego maintains a representation of the desired and actual LRPs, and moves the total state of actual LRPs toward the total state of desired LRPs by creating and destroying LRPs if requirements change, or in response to crashes or network failures.
  
  Diego's Receptor components recieve requests to add or delete LRP instances, such as app instances, using a [RESTful HTTP API](https://github.com/cloudfoundry-incubator/receptor/blob/master/doc/README.md).
  
  Receptors manipulate Diego's representation of its desired LRPs in the [Bulletin Board System \(BBS\)](./diego-pedia.html#bbs), an up-to-date cache of the state of the Diego cluster (including a picture-in-time of all desired LRPs, running LRP instances, and inflight Tasks).
  
  The [Converger](./diego-pedia.html#converger) operates on the BBS periodically and broadcasts requests to start or stop LRPs as needed, based on a comparison of desired and actual LRPs.
  
  Diego's [Auctioneer](./diego-pedia.html#auctioneer) distributes Tasks and LRPs to the cluster of Diego Cells via an [Auction](https://github.com/cloudfoundry-incubator/auction) involving the Cell [Rep](./diego-pedia.html#rep)s.  Once a Task/LRP is assigned to a Cell, the [Executor](./diego-pedia.html#executor) spins up a [Garden](./diego-pedia.html#garden) container and executes the work encoded in the Task/LRP.  This work is encoded as a generic, platform-independent, recipe of composable [actions](https://github.com/cloudfoundry-incubator/receptor/blob/master/doc/actions.md).
  
  Diego interfaces with [doppler](./diego-pedia.html#doppler) to provide real-time streaming logs for all Tasks/LRPs.  Diego also interfaces with the [gorouter](./diego-pedia.html#router) to automatically route web traffic to running LRP instances.
  
  ## <a id='diego-cf'></a> Diego and Cloud Foundry
  
  
negative.code: 
  Diego is a complex system with many moving parts. The interactions and high-level behavior of an entire Diego runtime deployment can be monitored and tested using the following releases:
  
  ### <a id='inigo'></a>Inigo
  
  - is an integration test suite that launches the various Diego components and excercises them through various test cases.  As such, Inigo *validates* that a given set of component versions are mutually compatible.
  
  