Yep. Um, usually we build those things because, uh, there's a lot of - there's a - like, when you're talking to a publisher, they want to see something, or if you're talking, to, like - uh, in Canada, we take a - a lot of advantage of government supports and the government applications require, like, a design document. Um, we don't - like, so usually, we do those - we create those documents for the purposes of, uh, those things. But um, I've found that, like, we'll create those things pretty early in the project, and then at the end of the project, we've kind of stuck to it. Not that we would have necessarily needed to create that document or that we're referring to that document along the course of the project, but it - those documents just by writing them, you - you're forced to answer, like, key design questions, and so, you end up solving a lot of the more difficult problems up front. And uh - and while you don't - we don't maintain them for the course of the project and make sure - because we're a very small team and everyone kind of knows what - what's happening as the project goes along, uh, it's too much maintenance work to keep updating those things all the time. So, um, but in the end, even though you haven't updated that document for a year and a half, you look back at it and you're, like, oh wow, it looks really similar to what we designed way back at - at the beginning, so.
