Repository contains business logic

How to fix

1. Move workflow decisions into a service or domain object.
2. Keep repository methods explicit about read/write behavior.
3. Test business branching outside the repository layer.

What the rule validates

A repository appears to make business decisions while reading or writing data.

Why it matters

Repositories should expose persistence operations without hiding policy or workflow behavior in data access.

Common causes

• A data helper grew into a workflow.
• Conditional business rules were placed near database queries.
• Persistence code performs side effects beyond storage.

Typical violation example

OrderRepository decides whether a refund is allowed before updating payment rows.

Typical compliant example

RefundService decides eligibility, then asks OrderRepository to persist the approved change.

Related rules

Adjacent categories

Related files/config

• apps/api/src
• apps/web
• packages

Related CLI commands

• archpilot validate
• archpilot validate --ci