I think there's a misunderstanding here. Both Gravity and Air have significantly higher BOMs than midsize. Higher BOMs mean more ECUs, wiring, chips, etc., that have to communicate with each other. Each one means more failure points.
With midsize, Marc Winterhoff has confirmed that their BOM is lower than their should-costs. This means reduced part counts, less ECUs, less chips, less components, etc. This will allow for the software team to focus on less varying systems and instead build strong foundations from the ground up. And the learnings from here can hopefully be translated into Air and Gravity for better user software experience.
And before you try and come to say I'm talking out of my ass, I come from working R&D in heavy industry steelmaking, then transitioned into a data science role having to develop complete end-to-end data pipelines for production. I know how much of a nightmare complex BOMs can be, and at the same time, I know how much a nightmare it is to develop software when the project owner is trying to add too much at the same time. By cutting back and focusing on less complexity, you can establish a more robust foundation for your software to grow.