is a nice series explaining what is wanted and talks about further iteration, but how can this happen in parallel or complementary if there is an environment that is doing SCRUM by the book?
I am mostly concerned about the time for meetings, since the ideal in this project is to make the engineers who will develop somewhat part of the design process to increase agency and accountability.
First, I would evaluate if having a formal system design process is correct for your organization. I don't know what level you are or the company you work at, so this is hard to tell. Here's some thoughts in a vacuum:
If you are going to formally bake in system design into your agile scrum system, just turn it into a task and assign points to it. That's what I effectively did when planning timelines for big projects at Meta: I would carve out 1-2 weeks just for the system design and planning. The failure mode (as you alluded to) is when you add on this extra thing but the existing timeline stays the same. Now you have too much on your plate as doing both the system design and execution is too much.