This makes a ton of sense. We're still fleshing the UX on this out a ton. I would post on the GitHub issue wrt to public and maybe make a new issue that asks about auditing. We've discussed auditing a bit internally, but want to collect use cases from users before implementing anything concrete. The v0 API has a "watch" functionally that can be used to tail all changes, but that might lose context from your app. In the past, we've typically kept audit logs at the app layer so we could attach as much metadata as possible.