So let's think about what a tool built for the decision layer would look like. It'd be a tool built for docs and not chat. And there's that's like a short sentence. There's a lot to unpack here though. So I'm going to spend a lot of time on this slide. The problem with chats is that they are the relic of building for implementation. So they're they're default isolated and ephemeral and and brain off. They're they're made to build things and get stuff done. And that's not really the same type of work we're doing at the decision layer. We're doing this creative exploratory work. So being in this isolated environment where I'm working with an agent, maybe I start with my vague idea and I'm exploring it and asking questions, but decisions are being made in that like that chat that are are not shared with my team that are going to disappear as as long I'm going to result in some code being output where those important decisions are not being made clear and shared with the team. And you're also in this mode where the agent saying Okay, this is what I want to do. Is is that okay? Let's go. Or or sometimes it'll say it'll ask you a question and it'll be like you know, this is the recommended option and then you're like, great. I don't even think about this. I'll just hit that one and we keep going. Docs start to solve this problem. So when you're if you center your work around working in docs they're meant to be bring forward the key decisions. This is this is what our work is now. Our work now is figure out what decisions matter and then make those decisions and then get out of the way while the