backend-feature-dev

To add a backend feature without architectural drift, implement domain logic, application services, infrastructure adapters, and tests using established patterns like domain-driven design and JPA separation. This ensures architecture compliance across the entire feature workflow.

Enforcing domain-driven design and authorization rules requires applying ADR-aligned implementation practices during use case development. This includes following specific patterns for REST endpoints, persistence changes, and access-control tests to maintain consistency.

Structure database migrations and JPA persistence changes by separating infrastructure adapters from domain logic. Apply ADR-aligned conventions to ensure database migration and event-driven practices satisfy the project's established architectural guardrails.

Yes, you can implement event listeners and access-control tests alongside new application services. The workflow guides development from domain behavior through infrastructure integration, satisfying authorization, testing, and event-driven requirements consistently.

Yes, the workflow supports Spring Modulith and Arrow Either integration. Architecture compliance explicitly enforces these framework patterns alongside Kotlin, JPA separation, and established authorization conventions for robust backend feature delivery.

Backend use cases suffer from inconsistent authorization and incomplete testing due to architectural drift. Applying guided implementation practices for domain logic, access-control rules, and required tests prevents these persistence and validation mistakes.