Philosophy

Pulsar deliberately trades some Laravel placement flexibility for a governed architecture boundary. Read this section to understand that choice before applying the detailed architecture rules.

Choose a principle

If you need to understand…	Read…
Why the Domain can use Laravel and still stay independent of delivery	Why Pulsar is Laravel-first
Which types Pulsar governs and which Laravel seams remain conventional	The app/Pulsar architecture boundary
Why Services are audiences rather than deployable systems	Services model audiences
When stock Laravel is the better choice and what Pulsar does not try to do	Trade-offs and non-goals

See Pulsar in context

Pulsar inside a Laravel application. Pulsar governs one explicit boundary inside a normal Laravel application; it does not replace Laravel.

Interpretation. Pulsar supplies architecture and generators for one directory inside the application. Laravel still boots and runs both governed Pulsar types and ordinary Laravel code, so adopting Pulsar does not create another runtime.

Continue by need

Evaluating adoption? Start with Choose how to adopt Pulsar. Ready for the exact placement and dependency rules? Continue to Architecture.

Philosophy owns the rationale for these choices; Architecture owns the detailed rules that enforce them.