I'm curious how others feel about validation living closer to the domain model, similar to Active Record validations in Rails. Laravel typically validates at the request or form layer, with database constraints and domain rules handled separately.

Would an optional model-level validation API improve consistency and reuse across HTTP requests, CLI commands, queued jobs, and imports, or would it blur responsibilities and encourage fat models?

If you've used both ecosystems, which trade-offs have mattered most in real projects?