Domain Exception
Domain Exception expresses a business-rule violation in the owning Domain.
Generated facts
- Layer
- domain
- Generated path
app/Pulsar/Domain/{Domain}/Exceptions/{Name}.php- Generator command
make:exception- Workflow method
- None
- Stability
- Current manifest surface (Pulsar 0.4.1)
Canonical example
Responsibility
Domain Exception owns the responsibility stated above; it must not absorb delivery, transaction, or unrelated cross-layer behavior.
Placement and dependencies
Keep this type in its generated Domain path. Domain is independent of delivery concerns; Infrastructure implements Domain-owned Contracts at its boundary.
Workflow and tests
Domain Exception is consumed by the owning Domain or Service workflow and returns a delivery-neutral result. Test its direct contract, its rejected boundary cases, and the caller or callee that proves the rule in application flow.
Three pitfalls
- ❌ Prohibited: move this responsibility into a neighboring type merely because it is nearby.
- ✅ Correct: keep the generated placement and depend only on the documented layer direction.
- ✅ Correct: test the boundary through the caller and the return or side effect visible to its callee.
Related reading
Read architecture placement for shared rationale and follow this page’s related concept links for the adjacent responsibility.
Boundaries
❌ Prohibited: Do not expose vendor-specific failures as Domain Exceptions.
✅ Correct: Translate vendor failures at the Infrastructure boundary.