Framework boundary
Pulsar governs generated architecture under app/Pulsar; Laravel still owns its conventional bootstrap and framework directories. The two can coexist while adoption proceeds route by route and module by module.
Concern ownership
| Concern | Owner | Reference |
|---|---|---|
| Generated Service, Domain, Infrastructure code | Pulsar | Directory structure |
| Migrations, factories, seeders, config, stock routes | Laravel | Architecture boundary |
| Relocated policy, listener, and Command discovery | Installer and provider | Installer |
Extension points
Use the generated PulsarServiceProvider for Contract-to-Adapter bindings, scoped services, gates, and optional observers. Generated Service providers remain explicit application registrations; make:service prints the class to add and does not silently patch bootstrap state.