anchor.diff:  Spores
   ------
   
  -The spore is the fundamental unit of modular software artifact production in Moss.
  -A spore describes how Moss produces artifacts from code in an architecture and toolchain independent fashion.
  +A spore describes how Moss produces artifacts from source code and files in an architecture and toolchain independent fashion.
   
   Definition
   ~~~~~~~~~~
  
positive.code: 
  Examples: host, amd64, cortex-m4, cortex-r7, avr, mipsel, etc.
  
  Code generated for different architectures does not interoperate and cannot be linked together.
  
  - `M.ARCHS`: All available architectures for current toolchain
  - `M.ARCH`: Current architecture for current toolchain
  
  Good discussion on architecture naming here: http://clang.llvm.org/docs/CrossCompilation.html
  
  Variants
  
negative.code: This document captures core design principles and concepts for the Moss build system.
  
  Moss produces completed software artifacts from source code.
  The core concepts in this process are:
  
  1. Spore - description of how to produce a final build artifact
  2. Code - content that must be compiled before being included in the artifact
  3. File - content that is directly used while forming the artifact
  3. Artifact - software build output with content from one or more spores
  
  Tools are used to produce artifacts from code.
  All tools with Moss to perform one of three actions:
  
  1. Transcode: source code -> source code
  2. Compile: source code -> object files
  3. Form: files + artifacts -> artifact
  
  Tools may be specialized according to:
  
  