docs/stories/010_time_class.txt
010_time_class
As a client
I can add facts to a fact stream and the time_stamp is set
* change valid? to errors
* returns array of error messages (errors.empty? indicates valid?)
* add a performance bench mark to the test set (this will also
act as a collision test for the randomization approaches).
* upgrade ruby 1.9.3 and 2.0.0
* use a TimeStamp class
* the to_s of this class shows the time_stamp to ns precision
* the TimeStamp.new accepts a larger_than: option that
works out the offsetting for being strictly larger than the
newest_time_stamp in a Fact collection in a graph
* the time_stamp class adds some random offset time
(e.g. between 1 and 999 ns) to a new time_stamp