Domain error file

Framework-agnostic errors

Service throws typed errors

No HTTP in service

No status codes in service

Route maps domain errors

Route re-throws unexpected

Route uses plain data

No SQL in service

Repo handles null

Plan describes flow

Factory/constructor injection

Dependencies typed as interfaces

Tests use injected mocks

No direct imports in service

Wiring shows real deps

No HTTP in service

Routes pass plain data

Service throws domain errors

Routes map errors to HTTP

No SQL in service

Tests are self-contained

No god service

Focused services per domain

Correct services/ directory

Correct repositories/ directory

Correct routes/ directory

Domain errors file

No SQL in services

No HTTP errors in services

No HTTP imports in services

Routes handle HTTP mapping

Telehealth service present

Restructure plan accurate

Side effects in services

Repository file exists

No SQL in service

No SQL in routes

Repo returns null for missing

Service decides on null

Repo maps to domain type

No business logic in repo

Routes pass plain data

No HTTP in service

Route re-throws unexpected errors

Types separated

Architecture notes layers

Shape validation in route

Business rules in service

No business logic in route

Side effects in service

No side effects in route

Service throws typed errors

Route maps errors to HTTP

Route re-throws unexpected errors

Separate repository module

No HTTP in service

Side effects notes accurate

Route passes plain data