anchor.diff:  
   Diego is the next-generation runtime powering Cloud Foundry (CF).
   
  -Diego schedules and runs **Tasks** and **Long Running Processes**:
  +Diego schedules and runs **[Tasks](./diego-pedia.html#tasks)** and **[Long Running Processes](./diego-pedia.html#lrps)**:
   
  -- A **Task** is a one-off job and is guaranteed to be run at most once.
  +Diego maintains a representation of the total set of desired and actual LRPs for a Cloud Foundry deployment, and constantly steers the set of actual LRPs toward matching the set of desired LRPs by creating and destroying LRPs as requirements change or in response to crashes or network failures.
   
  -- 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).
  +Diego's [Receptor](./diego-pedia.html#receptor) components recieve requests to add or delete LRP instances, such as app instances, via 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: 
   
  
positive.code: 
  The Auction package encodes the behavioral details around the [auction](./diego-auction.html).
  
  It 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).
  
  The [Auctioneer](./diego-pedia.html#auctioneer) and [Rep](./diego-pedia.html#rep) components use the Auction package to participate in the [auction](./diego-auction.html).
  
  
negative.code: 
  ### <a id='inigo'></a>Inigo
  
  Inigo is an integration test suite that launches the Diego components and excercises them through various test cases, including component failures and other exceptional cases.  As such, Inigo validates that a given set of component versions are mutually compatible, and that the system of these components is robust and degrades gracefully in its performance.
  
  [**Inigo on GitHub**](https://github.com/cloudfoundry-incubator/inigo)
  
  