laravel-domain-delivery

What problem does it solve?

Laravel changes often become risky and hard to verify because authorization, persistence shape, async side effects, caching, and deploy sequencing can be mixed or implicitly assumed.

Core Features & Use Cases

• Contract-first Laravel slice delivery: Keeps HTTP input, validation/authorization, Eloquent persistence, and orchestration in their framework-owned boundaries (Form Requests, Policies/Gates, models, services/actions, jobs/events, cache, migrations).
• Production verification evidence: Requires scoped commands, explicit proof of query shape and behavior constraints, and durable “workflow receipts” before claiming completion.
• Rollback discipline: Enforces reversible migrations or documented irreversible decisions, plus compatibility/feature-flag/queue-cache rollback plans for the changed slice.

Quick Start

Ask your AI to review and implement a small Laravel feature using Form Requests, Policies/Gates, Eloquent with proven query shape, focused tests, and a named rollback plan, and then run the required scoped verification command before final completion.