In #26866 we're introducing a new package called @wordpress/stan with its bindings with @wordpress/data. Read the PR description and the package README for more details.

Introducing a new way to register stores and deal with state is a big task and this issue is going to serve as a follow-up todo list:

• Try use-subscription for use-select (check the performance results) Data: Implement atomic stores #26866 (comment)
• Check how @wordpress/data bindings perform in concurrent mode Data: Implement atomic stores #26866 (comment)
• Introduce simple react bindings for @wordpress/stan for folks that don't want to use @wordpress/data (hook creator like zustand or provider based like jotai)
• Build ReduxDevTools integration Data: Implement atomic stores #26866 (comment)
• Stabillize and document the @wordpress/data bindings.
• Decide whether to keep stan as a bundled package or not.
• Replace the atom family concept with a more generic selector concept. Generalize the atom family concept as an atom selector concept instead #27147

In parallel, we can also start trying to refactor existing stores to atomic stores. This work is expected to have good impact on performance especially for central stores like block-editor

• core (entities)
• core/data (resolution state)
• core/block-editor
• core/editor
• core/viewport
• core/edit-post
• core/edit-widgets
• core/edit-site
• core/blocks @youknowriad Refactor the core/blocks store as an atomic store #27140

Feel free to own one of these tasks.