There is no misunderstanding to the purpose of services at all on your side. Since Lucid is a flexible architecture and is only providing the "shell" of your application, its principles do not dictate what the services are and which pattern is followed in creating them. It is use-case dependant so you may use it whichever way that's best for your purpose. Web, Api and Admin are just simple examples of one approach. Yours surely qualifies to be another where each of PM, HR and Chat gets their own space due to the degree of difference between their processes.

Just make sure you don't tangle responsibility and introduce cross dependency between them. You may use Domains and Data to share functionality instead, even if it meant to also have PM, HR and Chat domains to hold their functionalities (in addition to others), it would still make sense for each service to have its own commands, seeders, migrations, features, routes etc.

The boundaries are set by you and your team to ensure a consistent usage of the architecture.