Which method is preferred for extending Jetstream team roles without modifying core scaffolding?

Laravel Jetstream implements a team management system that leverages Laravel Fortify for authentication and utilizes Gates for role-based access control (RBAC). By default, the system provides a structured way to define team roles and permissions within the JetstreamServiceProvider.

When scaling an application, there is a need to implement dynamic or database-driven roles rather than hard-coded definitions in the service provider. Because Jetstream's scaffolding is designed to be installed once, modifying the core provider can lead to maintenance challenges during framework updates.

What is the recommended architectural approach to integrate a dynamic role management system while maintaining compatibility with Jetstream's built-in team membership logic? Does this require overriding the default team membership policies or implementing a custom middleware layer?