How did you determine in FSD what should go into a feature and what into another, given the overlaps in the store catalog?

In FSD (Feature-Sliced Design), defining feature boundaries is based on business logic and responsibility. If there are overlaps in the store catalog, the division into features is guided by:

• Feature responsibility: each feature is responsible for a specific set of tasks or business functions. For example, the "Catalog" feature handles displaying and filtering products, while the "Cart" feature manages selected items.
• Isolation and reusability: common parts used across multiple features are extracted into separate layers (e.g., shared or entities).
• Minimization of dependencies: efforts are made to minimize overlaps so that features are as independent as possible.

Thus, if overlaps exist in the catalog, they are isolated into separate entities or shared modules, and features utilize these common parts while maintaining responsibility for their specific functionality.