anchor.diff:  So it doesn't do <<incrementalScoreCalculation,deltas>>.
   Nor does it support <<explainingTheScore,justifications>>.
   
  -On the other hand, the `ConstraintStreams` API uses <<incrementalScoreCalculation,deltas>>
  +On the other hand, the ConstraintStreams API uses <<incrementalScoreCalculation,deltas>>
   and supports <<explainingTheScore,justifications>>:
   ////
   
  
positive.code: :experimental:
  
  
  Constraint streams are a functional programming form of incremental score calculation in plain Java that are easy to read, write, and debug. In OptaPlanner, contraint streams are implemented thorugh the `ConstraintStreams` API.This API should feel familiar if you have worked with Java 8 Streams or SQL.
  
  [WARNING]
  ====
  The `ConstraintStreams/ConstraintProvider` API is an ongoing project. It works but it has many API gaps. Therefore, it is not yet rich enough to handle complex constraints.
  <<explainingTheScore,Constraint justifications>> may not function properly.
  //COMMENT: Lukas, what specifically  might not function.  This link is to section 5.6, Explaining the score: which constraints are broken?  Or maybe we don't need to worry about this based on your comment below?
  ====
  
  // TODO Remove the previous sentence when PLANNER-1709 is fixed.
  
  To use constraint streams in your project, implement the `ConstraintProvider` interface and inlcude the following code in your solver configuration:
  //COMMENET: Is adding the code how you implement `ConstraintProvider` or do I need to do both: Implement `ConstraintProvider` and add the code to my solve configuration?
  
  [source,xml,options="nowrap"]
  ----
  
negative.code: 
  
  [[constraintStreamsFilter]]
  == Filter
  
  image::ConstraintStreams/constraintStreamFilter.png[align="center"]
  
  
  [[constraintStreamsJoin]]
  == Join
  
  image::ConstraintStreams/constraintStreamJoinWithoutJoiners.png[align="center"]
  
  