Is it a good practice to use a single Builder pattern for both creating and updating an entity?

A developer is evaluating whether one TypeScript PermissionBuilder should handle both create and update flows.

Create requires fields like name and module, while update requires id and may allow partial changes to other fields.

The question is whether to reuse one builder with mode-based validation or split into separate CreatePermissionBuilder and UpdatePermissionBuilder classes.

The choice impacts validation clarity, maintainability, and safe handling of payloads in a Node.js backend and repository layer.