Layers and dependency directionintermediate
Splitting a system into layers only means something if the dependencies point one way — the rule that the DTO layer cannot see an entity is what stops your database schema quietly becoming your public API.
Seven files, seven projects, and one rule that does most of the work: the DTO layer must not be able to see an entity. Place each file where the dependency graph allows it.
AssumesVertical Slice RefactorThis sprint argues the opposite side of the vertical-slice refactor. It reads as dogma without the case it is answering.
No project references one above it, and no entity type appears in Application.Contracts.
Published in full, before you start — every point is one of these and there is nothing else.
Splitting a system into layers only means something if the dependencies point one way — the rule that the DTO layer cannot see an entity is what stops your database schema quietly becoming your public API.