I'm thinking along the lines of redux, where the state is a function of an initial state, and mutations carried out by reducers.

The benefit is that mutations can capture a large amount of information, and as requirements change, the reducers can be modified to produce a new state.

Also, we have a history built in.

Is this a common pattern in database design?

Specifically, I'm considering implementing this on Firestore. What should I know?