Clojurians Log v2

Great question :) It can be tempting to apply valid time in many scenarios but we can generally only recommend that it's appropriate when you're trying to model the notion of an upstream observation/action time, i.e. when there's been a delay Otherwise your mileage may vary, although you can certainly build some interesting things if you want to get creative

So that leaves using write-time and model some custom applicative time for messages (like you would in normal sql)

write-time feels like more for auditing than applicative usage...

Auditing may be overly specific - I think of it more like "trying to make sense of what has happened" which covers all kinds of analysis

System time (transaction time) is purely for system audit and read consistency