service-business-logic

What problem does it solve?

It prevents application services from becoming fragile, insecure, and inconsistent by defining how to coordinate authorization, domain operations, persistence, events, and external effects within a clear use-case boundary.

Core Features & Use Cases

• Authorization-first orchestration: Ensures policy checks happen before any repository read to avoid information disclosure and timing side channels.
• Explicit transaction boundaries: Separates in-transaction domain/repository work from out-of-transaction external calls to prevent rollback-after-external-call inconsistencies.
• Domain-invariant delegation: Keeps business rules in the domain layer so services don’t duplicate invariants and drift over time.
• Anti-god-service guidance: Enforces single-responsibility use-case services rather than bundling unrelated workflows into one service.

Quick Start

Ask the agent to design a single bounded service method for your change scenario, including the authorization order, explicit transaction scope, domain calls, repository actions, event emission timing, and external-effect compensation plan.