anchor.diff:  <div class="page-header" id="welcome">
  -  <h1>Welcome to Daimio!</h1>
  +  <h2>Preface</h2>
   </div>
   
   This document serves as a primer, tutorial, specification, test suite and REPL for the Daimio language.
  
positive.code:   <h2>In Depth: Variables</h2>
  </div>
      
      ----- talk about pipeline vars, injected vars, imported vars, and then space vars
      
      (so pipelines are actually DAGs)
  
negative.code:         777
  
  
  <div class="page-header" id="id_pipeline_parallelism">
    <h2>Some notes on pipeline parallelism</h2>
  </div>
  
  A few example pipelines we can parallelize internally.
  
  //    {  123 
  //     | >in | add 1 | >out1
  //    || _in | add 2 | >out2
  //    || _in | add 3 | >out3
  //    || (out1 out2 out3)}
  Those three middle pipelines could run in parallel.
  
  //    {123 | (
  //      {__ | add 1}
  //      {__ | add 2}
  //      {__ | add 3}
  //    )}
  
  //    {123 | (
  //      {__ | add $x | $>x}
  //      {__ | add $x | $>x}
  //      {__ | add $x | $>x}
  //    )}
  
  That last one leads to non-determinism if you parallelize without fixing the execution order. 
  
  If we're going to allow in-pipeline parallelism, we open up two questions: 
  1) what is $x inside each pipeline?
  2) what is $x at the end? 
  
  And probably, the answers are
  1) A separate copy of the initial $x for each pipeline (clearly this hurts performance, but a: we don't care b: don't use space vars in parallel pipelines c: don't be daft)
  2) Last Write Wins, in expressed order [does compilation ever hurt reasoning about this, or is it guaranteed order invariant?]
  
  EXCEPT. Except if we do the above, $x is completely different at the end than if we don't run in parallel. 
  SO: space vars CAN NOT be written in pipelines run in parallel -- writing a space var forces the entire sequence to be run sequentially. 
  Same holds true for writing to like-named pipeline vars: those are errors, and force sequential execution.
  
  
  <div class="page-header" id="id_app_known">
    <h2>Known Bugs</h2>
  </div>
  
      Keyed lists with positive integer keys are not ordered correctly. All keyed lists should be ordered by insertion order by default, and retain their sort order if sorted. Even once this is fixed imports from JSON will still have this problem (for the initial import, not once sorted) unless we write our own JSON parser.
  