Q Within that, you mentioned a couple of industries. And so, uh, There are large legacy industries that haven't caught many of the waves of innovation throughout time because, you know, they're more laborious. It's like physical demand. Um, what exactly are you targeting with Zoo? Like, is there a particular part in the process for further hardware development? Is this like a specific niche in the industry?
A Yeah, to narrow it down, we start at the design phase of the hardware development lifecycle. You know, there's various elements that go into Uh, generating design and getting something into production for an actual, you know, engineered, manufactured part. And we start on the design side where it's actually generating the geometry, generating what eventually gets made downstream. We don't touch that downstream area yet. We will be soon. And, and the intent of that is to capture essentially industry-wide, you know, once you have the geometric primitives, all those shapes, all the computation to combine those shapes together into more and more complex geometric Uh, parts, you know, engineered designs. Then there's no one specific industry that's optimized for, for all of them, because those primitives can be combined in a way that forms shapes for any industry. But the people who we tend to see the most adoption from are people that see software development and hardware development side by side. There's an asymmetry there. Where in modern software development, you can write code at scale. You can push that to the cloud. To dynamically allocate that, dynamically scale that. Then you can write unit tests. You can write, um, what is called continuous integration workflows, where you automatically make a software edit that automatically gets tested to verify that works well, and that…
AI assessment note: “we start at the design phase of the hardware development lifecycle.”