Your /Models folder is lying to you

The article argues that the common practice of placing all data classes into a single Models/ folder in .NET projects obscures scope, ownership, and lifetime of those classes. It categorizes POCOs into four roles—private internals, feature-scoped contracts, genuinely shared models, and sub-components—and advocates treating internal models like private functions by nesting them inside the services that use them.