Robot's Clean Approach - Revision history

Iwiseman: /* UI (or Presentation) */

2026-02-17T06:41:01Z

UI (or Presentation)

← Older revision		Revision as of 06:41, 17 February 2026
Line 45:		Line 45:

	Typical things here:		Typical things here:
	- ViewModels		* ViewModels
	- Commands		* Commands
	- Data binding adapters		* Data binding adapters
	- UI‑specific formatting		* UI‑specific formatting
	- Brushes, colors, visual state logic		* Brushes, colors, visual state logic

	Your mental cue		Your mental cue
Line 59:		Line 59:
	> "What does this thing need to know about?"		> "What does this thing need to know about?"

	- If it needs UI → it's UI.		* If it needs UI → it's UI.
	- If it needs infrastructure → it's infrastructure.		* If it needs infrastructure → it's infrastructure.
	- If it needs domain → it's application or domain.		* If it needs domain → it's application or domain.
	- If it needs nothing → it's domain.		* If it needs nothing → it's domain.

Iwiseman: /* Infrastructure */

2026-02-17T06:40:37Z

Infrastructure

← Older revision		Revision as of 06:40, 17 February 2026
Line 31:		Line 31:

	Typical things here:		Typical things here:
	- EF repositories		* EF repositories
	- File system access		* File system access
	- HTTP clients		* HTTP clients
	- Logging implementations		* Logging implementations
	- Anything that touches OS, network, or frameworks		* Anything that touches OS, network, or frameworks

	Your mental cue		Your mental cue

Iwiseman: /* Application (Use Cases) */

2026-02-17T06:40:23Z

Application (Use Cases)

← Older revision		Revision as of 06:40, 17 February 2026
Line 18:		Line 18:

	Typical things here:		Typical things here:
	- Use case classes (e.g., LocateMissingTracks)		* Use case classes (e.g., LocateMissingTracks)
	- Input/output models for use cases		* Input/output models for use cases
	- Interfaces for persistence, file access, external services		* Interfaces for persistence, file access, external services
	- Transaction boundaries		* Transaction boundaries

	Your mental cue		Your mental cue

Iwiseman: /* Domain */

2026-02-17T06:40:11Z

Domain

← Older revision		Revision as of 06:40, 17 February 2026
Line 4:		Line 4:

	Typical things here:		Typical things here:
	- Entities		* Entities
	- Value objects		* Value objects
	- Domain services		* Domain services
	- Domain events		* Domain events
	- Pure logic with no external dependencies		* Pure logic with no external dependencies

	Your mental cue		Your mental cue

Iwiseman: /* Application (Use Cases)= */

2026-02-17T06:39:53Z

Application (Use Cases)=

← Older revision		Revision as of 06:39, 17 February 2026
Line 13:		Line 13:
	If it would still make sense in a console app with no UI, no database, no internet → Domain.		If it would still make sense in a console app with no UI, no database, no internet → Domain.

	=Application (Use Cases)==		=Application (Use Cases)=
	Question: "Does this orchestrate domain logic to achieve a user‑level goal?"		Question: "Does this orchestrate domain logic to achieve a user‑level goal?"
	If yes → Application.		If yes → Application.

Iwiseman: Created page with "=Domain= Question: "Does this represent business meaning, rules, or invariants?" If yes → Domain. Typical things here: - Entities - Value objects - Domain services - Domain events - Pure logic with no external dependencies Your mental cue If it would still make sense in a console app with no UI, no database, no internet → Domain. =Application (Use Cases)== Question: "Does this orchestrate domain logic to achieve a user‑level goal?" If yes → Appli..."

2026-02-17T06:39:43Z

Created page with "=Domain= Question: "Does this represent business meaning, rules, or invariants?" If yes → Domain. Typical things here: - Entities - Value objects - Domain services - Domain events - Pure logic with no external dependencies Your mental cue If it would still make sense in a console app with no UI, no database, no internet → Domain. =Application (Use Cases)== Question: "Does this orchestrate domain logic to achieve a user‑level goal?" If yes → Appli..."

New page

=Domain=
Question: "Does this represent business meaning, rules, or invariants?"
If yes → Domain.

Typical things here:
- Entities
- Value objects
- Domain services
- Domain events
- Pure logic with no external dependencies

Your mental cue
If it would still make sense in a console app with no UI, no database, no internet → Domain.

=Application (Use Cases)==
Question: "Does this orchestrate domain logic to achieve a user‑level goal?"
If yes → Application.

Typical things here:
- Use case classes (e.g., LocateMissingTracks)
- Input/output models for use cases
- Interfaces for persistence, file access, external services
- Transaction boundaries

Your mental cue
If it coordinates domain objects but doesn't know how they're stored → Application.

=Infrastructure=
Question: "Does this talk to the outside world?"
If yes → Infrastructure.

Typical things here:
- EF repositories
- File system access
- HTTP clients
- Logging implementations
- Anything that touches OS, network, or frameworks

Your mental cue
If it deals with how something is done (not what or why) → Infrastructure.

= UI (or Presentation)=
Question: "Does this exist only because humans need to see or interact with it?"
If yes → UI.

Typical things here:
- ViewModels
- Commands
- Data binding adapters
- UI‑specific formatting
- Brushes, colors, visual state logic

Your mental cue
If it's about display, interaction, or state for the screen → UI.

🎯 The trick: When you're unsure, ask the dependency question
If you're stuck on where something goes, ask:

> "What does this thing need to know about?"

- If it needs UI → it's UI.
- If it needs infrastructure → it's infrastructure.
- If it needs domain → it's application or domain.
- If it needs nothing → it's domain.