[holoway]

It's a good question! Having a history of how things transformed over time matters. We keep track of that in a couple of ways - one is the graph snapshots themselves, and the other is a raw history log. It's really just another view of a snapshot of the graph at a particular time, and a delta between that graph and the current.

We have lots of planned work coming here - but we have a very rich dataset to do it from, and we're stoked to get there.

[eikenberry]

Having the history of changes is a step, but the important part of that is the why those changes were made. Git can capture this with good commit messages. Do you have any plans to capture that "why"?

[thayne]

Another nice thing about using code is you can easily include comments explaining why something is done a certain way, right next to the code that does it and thay is also included in the history.

[holoway]

Yep! The application of Change Sets is a similar moment to record the "why", alongside all the information about what was done. We have more to do here, along with adding things like RBAC that requires review before change sets can be applied based on ownership of resources, etc. But this is the plan!

[eikenberry]

Thanks for answering my questions! Look forward to playing with it.