This is golden, and not just for reports. If you expose the change data stream as an API, many integrations become 10x simpler for your partners and customers.

This is golden, and not just for reports. If you expose the change data stream as an API, many integrations become 10x simpler for your partners and customers. Providing a consistent definition for read-after-write (or search specifically) will make this even better. This is often problematic because the search index is often a different store and there are lags between primary writes and search index. Many bi-directional integrations need consistent read-after-write capabilities, or at least some way to tell how current the read paths are. I say this as a founder of a company with a significant part of the product doing integrations with other systems. And most are painful.