@jasongorman it's quite a telescopic statement. On one side of it is data as-stored, on the other side of it is data as-used. One informs the other and the correct way is to go from usage to storage. But be too literal and you risk to forget stuff that isn't used yet! More sustainable way to think about it, imo, would be to connect "as-used" lens of the telescope directly to "as-presented", which (and there can be no argument about it) then informs the "as-stored" lens. That's why projections in event sourcing and VIEWs in SQL are so important. Arguably, that allows for separation of concerns!