anchor.diff:  
   ## Is Lattice ready for production?
   
  -Diego, the runtime component of Lattice is not in production yet with Cloud Foundry. Diego is planned for production use sometime late in Q1 of 2015.
  +Diego, the runtime component of Lattice is not in full production yet with Cloud Foundry, but is running a subset of [Pivotal Web Services](https://run.pivotal.io/) deployments. Diego is planned for full production use sometime early in Q2 of 2015.
   
   The Router and Loggregator components of Lattice have been in production with Cloud Foundry for over a year and we consider them production-ready.
   
  -The deployment strategy employed by Lattice emphasizes convenience and simplicity.  When deployed with Terraform none of the Lattice VMs are monitored - should a VM fail it will not be recreated.  Moreover, Lattice minimizes overhead by running single instances of several components.  These constitute single-points of failure and should not be relied upon in a production setting.  If you'd like to set up a productionized deployment of Lattice we recommend deploying CF + Diego with BOSH.  Instructions for this are available on the [Diego-Release GitHub repository](https://github.com/cloudfoundry-incubator/diego-release).
  +The deployment strategy employed by Lattice emphasizes convenience and simplicity.  When deployed with Terraform none of the Lattice VMs are monitored - should a VM fail it will not be recreated.  Moreover, Lattice minimizes overhead by running single instances of several components.  These constitute single-points of failure and should not be relied upon in a production setting.  If you need to set up a productionized deployment of Lattice you will need to be sure to make all the components redundant, plus provide monitoring and management on the hosts. As the project evolves and there is more experience in the community, we hope those solutions will emerge and be shared. Depending on the use case, we also recommend considering deploying Cloud Foundry with BOSH. Instructions for this are available on the [Diego-Release GitHub repository](https://github.com/cloudfoundry-incubator/diego-release).
   
   ## How secure is Lattice?
   
   Security is not Lattice's primary concern.  Lattice is intended to provide a cluster root experience with minimal barriers to entry.  Multi-tenant workloads are not in scope.  Additionally, no effort is made to prevent containers from communicating with other components within a Lattice cluster.  Also, no effort is made to protect log streams behind an authentication layer - they are accessible to clients with network access to Lattice servers.
   
  -If you would like to explore a secure deployment of Lattice we recommend BOSH deploying CF + Diego.  Instructions for this are available on the [Diego-Release GitHub repository](https://github.com/cloudfoundry-incubator/diego-release).
  +As the project evolves and there is more experience in the community, we hope security solutions will emerge and be shared. Depending on the use case and security needs, we also recommend considering deploying Cloud Foundry with BOSH. Instructions for this are available on the [Diego-Release GitHub repository](https://github.com/cloudfoundry-incubator/diego-release).
   
   ## What Operating Systems are supported?
   
  
positive.code: 
  ## What is the relationship between Lattice and Diego?
  
  [Diego](https://github.com/cloudfoundry-incubator/diego-design-notes) is Cloud Foundry's next generation elastic runtime.  Lattice is essentially a stripped down distribution of Diego that eschews most of Cloud Foundry's enterprise features.  Lattice is built to let you deploy and interact with Diego with ease.  New features that make their way into Diego will be available on Lattice almost immediately.
  
  To build a deep understanding of how Lattice works you'll need to learn about Diego.  The [design notes](https://github.com/cloudfoundry-incubator/diego-design-notes) are a good starting point for building a mental model of what is going on under the hood.
  
  
negative.code: 
  Lattice containers are described as long-running processes or temporary tasks. Lattice includes support for Linux Containers expressed either as Docker Images or by composing applications as binary code on top of a root file system. Lattice's container pluggability will enable other backends such as [Windows](https://www.youtube.com/watch?v=S4U_YyzC5z4) or [Rocket](http://blog.pivotal.io/cloud-foundry-pivotal/news-2/launching-rockets-collaborating-on-next-level-linux-containers) in the future.
  
  All this functionality leverages components of [Cloud Foundry](https://github.com/cloudfoundry). The new parts in Lattice are the CLI to interact with the component APIs and the installers.
  
  ## Why did we create Lattice?
  
  We wanted to be able to leverage components of Cloud Foundry independently to demonstrate the capabilities and facilitate more rapid experimentation. We believe these components are already useful in their own right, but will also improve with more wide adoption and exposure.
     
  We also have a strong opinions on the developer and operator experience for scalable applications that we hoped to express with Lattice. Our foundational principles are:
  
  - **Simple**: you should be able to get started in minutes.
  - **Comprehensive**: include capabilities commonly required for scalable applications.
  - **Extensible**: you should be able to use it how you like, adding and taking away things.
  
  
  Lattice lives up to these principles.
  
  