Is There a Technical Reason for Splitting Models Into Aggregate Models?

I think my theory is that for simple applications, you will only need one aggregate model. You can even call it model. That's fine with a capital M. And that will provide you all the data you need with like different different structs. But as your business needs evolve and now you need to keep track of inventory or fulfillment... Then you start adding different aggregate model or facades,. whichever one you want. Those will be responsible for giving you different kind of model data that will, you know, be displayed and manipulated on the screen.