then once we have stored it, part of storing it is making sure that it is going to be there when we go to look for it again. We have to make sure that it is stored persistently and it is not evaporative. It is not contingent on power. It is not stateless. It is not going to disappear the next time the browser refreshes, right? Critical. We have to make sure the storage piece is solid, that when we store it and commit it, that it will be there. Then subsequently, there is a secondary process that takes it from there and makes a second copy of it on another server physically. For right now, we will put that secondary DR piece aside that later on can be the STORJ.io network, which is Amazon S3 compatible. Any tools or connectors we want to use should be able to use that functionality from STORJ.io, which we can connect to and provide keys to in any case.

One more thing to add to this: I think it would make sense to ask the architect once more about all of this. Really again, how can we re-visualize this dashboard so that there is more information that we can present on the front end to be able to make these decisions? It is more at the ready. There is more color, more icons, more clear recognition of what is more clear definition of what the information suggests in terms of what actions we should be taking, what is actionable, which we would be doing in what order, why, and according to what lens. How do we know that? How do we take action on that? What would happen when we do take action on that? What are the sequences of events that get kicked off when we hit the button? What happens next? What part of that process makes sure that we stay on path until we get to the last stage, which is deploy? What's the point with the platform if the user gets stuck, or caught up, confused, or otherwise impeded, caught in the mire? They get literally stuck in the bog in the swamp, literally stuck at one of these stages for one reason or another. How do we make sure they get all the way to the end? What kind of a system can be put into place? What kind of a reminder notification, a project management system, so that when these analyses are made there is a timer stopwatch? There is something that is keeping track of when these initial ideas were created and what time it is now, what has transpired, and when is too much time in between stages, or how to best gauge what each stage should take so that the user is aware? The system could say, "Okay, it is noon on a Tuesday on this date. This should take about two hours. You should be done by such and such a time, and then you can start on the next phase, which will take about this much time. If you work from now until then, stopping for meals and exercise, you should be able to finish this by this date at this cost or required usage of resource or AI or whatnot, something of that nature." It will result in this outcome for you, this new scalability for the app, or otherwise.