Presentation layer - ANSWER Handles user interaction such as screens menus
routes and basic formatting. Should not contain business rules or database code.
Controller - ANSWER Directs the user flow by reading input calling application
services and choosing what to show next.
View - ANSWER Displays information to the user such as console output web
pages or UI widgets.
View model - ANSWER Data shaped for display so the UI can render easily
without extra logic.
Presenter - ANSWER Prepares display ready text and values so views stay
simple.
Input output helper - ANSWER Reusable code for reading and writing at the UI
boundary such as prompt read int and print.
Routing - ANSWER Maps user actions or URLs to controller handlers.
Request handler - ANSWER Receives an input event and calls the correct use
case then returns a response.
Response model - ANSWER Data shape returned to the UI that is safe to display.
Application layer - ANSWER Implements use cases which are the actions the
system can perform. Coordinates domain and data access.
Application service - ANSWER Implements a system action such as create habit
or checkout. Enforces business rules and calls repositories.
Use case - ANSWER A single user goal expressed as an operation such as create
habit mark completed or register user.
Interactor - ANSWER Another name for a use case class that performs one
focused operation.
Command object - ANSWER Holds input data needed to run a use case without
adding business behavior.
