I’m quite familiar with Redux Toolkit, and in fact use it quite extensively in this tutorial on building your own MFE I wrote some time ago. During the Open edX conference, I had my two hour workshop running through all the components needed to set up a very basic MFE that just did the work of displaying a course catalog. Almost all of the time spent was on making Redux work, even with the benefits of Redux Toolkit.
Then, in the last five to ten minutes or so, I had the learners rewrite the MFE’s state management using Providence instead. It eliminated several files of work from the project and replaced them with only a few lines.
This is because Providence works on a higher abstraction layer than Redux and Redux Toolkit do. In fact, Providence uses Redux Toolkit to build out the stores and automations it makes.
To do this, it does make some assumptions about use cases and the data. However these assumptions do fit 90+% of the use cases we use Redux for, and for those it does not cover, Providence works seamlessly alongside traditionally built Redux stores without getting in the way. It can be easily added to existing MFEs without breaking existing stores.
The article you link is describing an event that happened in the past to have technologies accepted. At the time this article was created, Providence did not yet exist. What work does Providence need to go through to get to accepted status?