anchor.diff:  
   ## <a id='brain-components'></a> Diego Brain Components
   
  -
  -### <a id=''></a> Auctioneer
  -
  -[**Auctioneer**](https://github.com/cloudfoundry-incubator/auctioneer)
  +### <a id='auctioneer'></a> Auctioneer
   
   - holds auctions for Tasks and ActualLRP instances.
  +
   - auctions are run using the [auction](https://github.com/cloudfoundry-incubator/auction) package.  Auction communication goes over HTTP and is between the Auctioneer and the Cell Reps.
  +
   - maintains a lock in the BBS such that ***only one*** auctioneer may handles auctions at a time.
   
  +[**Auctioneer on GitHub**](https://github.com/cloudfoundry-incubator/auctioneer)
  +
   ### <a id=''></a> Converger
   
  -[**Converger**](https://github.com/cloudfoundry-incubator/converger)
  -
   - maintains a lock in the BBS to ensure that ***only one*** converger performs convergence.  This is primarily for performance considerations.  Convergence should be idempotent.
  +
   - uses the converge methods in the runtime-schema/bbs to ensure eventual consistency and fault tolerance for Tasks and LRPs
  +
   - when converging LRPs, the converger uses identifies which actions need to take place to bring DesiredLRP state and ActualLRP state into accord.  Two actions are possible:
  -        - if an instance is missing, a start auction is sent.
  -        - if an extra instance is identified, a stop message is sent to the Rep on the Cell hosting the instance.
  +    - if an instance is missing, a start auction is sent.
  +    - if an extra instance is identified, a stop message is sent to the Rep on the Cell hosting the instance.
  +
   - in addition, the converger watches out for any potentially missed messages.  For example, if a Task has been in the PENDING state for too long it's possible that the request to hold an auction for the Task never made it to the Auctioneer.  In this case the Converger is responsible for resending the auction message.
   
  -### <a id=''></a> Metrics
  -
  -[**Metrics-Server**](https://github.com/cloudfoundry-incubator/runtime-metrics-server)
  -
  -- reads metrics from the BBS and publishes them to Doppler.
  -
  -## <a id='shim-like-components'></a>Additional (shim-like) components
  -
  -- [**Route-Emitter**](https://github.com/cloudfoundry-incubator/route-emitter)
  +[**Converger on GitHub**](https://github.com/cloudfoundry-incubator/converger)
  +
  +### <a id='metrics'></a> Metrics
  +
  +Reads metrics from the BBS and publishes them to Doppler.
  +
  +[**Metrics-Server on GitHub**](https://github.com/cloudfoundry-incubator/runtime-metrics-server)
  +
  +## <a id='shim-like-components'></a>Shim-like components
  +
  +### <a id='route-emitter'></a>Route-Emitter
  +
   - monitors DesiredLRP state and ActualLRP state via the Receptor.  When a change is detected, the Route-Emitter emits route registration/unregistration messages to the [router](https://github.com/cloudfoundry/gorouter)
  +
   - periodically emits the entire routing table to the router.
  +
   - someday the route-emitter will be a part of the router, which will communicate with the Receptor to compute the routing table.
   
  +[**Route-Emitter on GitHub**](https://github.com/cloudfoundry-incubator/route-emitter)
  +
   ## <a id='platform-specific-components'></a>Platform-Specific Components
   
   Diego is largely platform-agnostic.  All platform-specific concerns are delegated to two types of components: the *garden backends* and the *app lifecycles*.
   
   ### <a id='garden-backends'></a>Garden Backends
   
  -[**Garden**](https://github.com/cloudfoundry-incubator/garden) contains a set of interfaces each platform-specific backend must implement. These interfaces contain methods to perform the following actions:
  +Garden contains a set of interfaces each platform-specific backend must implement. These interfaces contain methods to perform the following actions:
   
   - create/delete containers
   - apply resource limits to containers
  
positive.code: 
  [**Executor on GitHub**](https://github.com/cloudfoundry-incubator/executor)
  
  ### <a id=''></a> Garden
  
  - provides a platform-independent server/client to manage garden containers
  
  
negative.code: 
  ## <a id='other-components'></a>Other Components
  
  ###<a id='etcd'></a>ETCD
  
  - is the consistent store at the heart of diego
  
  - all components that access etcd do so via the runtime-schema/bbs.
  
  [**ETCD on GitHub**](https://github.com/coreos/etcd)
  
  ### <a id='storeadapter'></a>Storeadapter
  
  - provides a driver for interfacing with etcd.
  
  [**Storeadapter on GitHub**](https://github.com/cloudfoundry/storeadapter)