anchor.diff:  
   ==== Step 1
   
  -At some point in time you wonder about having a deadlock in your custom engine domain model.
  -You transform your domain model into the (simple) jtwfg-model using a graph builder object:
  +At some point in time you wonder about having a deadlock in your custom engine domain model objects.
  +You transform your domain model objects into the (simple) jtwfg model objects using a jtwfg graph builder object:
   
   [source,java]
   ----
  
positive.code: }
  ----
  
  === Scenario 2: "Update the jtwfg model" as you update your domain model and check for deadlocks on the fly
  
  Probably you want to keep the jtwfg model "in sync" with your domain model and check for deadlocks on the fly
  as soon as you update your model. Probably you use various threads to update your domain model and the jtwfg model.
  
  That's fine.
  
  
negative.code: 
  === Thread-safety of jtwfg
  
  For simplicity and comfort, the jtwfg 'GraphBuilder' and 'DeadlockDetector' classes are threadsafe.
  See the documentation in the source code for more information about thread-safety.
  
  If you would like to use jtwfg single-threaded and have performance issues, let me know.
  
  === Limitations of jtwfg
  
  At the moment only simple, synchronous dependencies are supported by jtwfg.
  
  == Requirements
  
  