https://www.brettryan.dev/tags/documentationasacontract/Recent content in DocumentationAsAContract on Brett RyanHugoenMon, 07 Sep 2026 10:28:31 +1000https://www.brettryan.dev/posts/week-three-wabe-labs-is-born/Thu, 10 Sep 2026 12:20:00 +1000https://www.brettryan.dev/posts/week-three-wabe-labs-is-born/<p>Entering the third week of my startup adventure has been a deeply rewarding time of solidifying foundations. Things come together to form an official brand, I put together tools to help with financial discipline, and I finished off the week by practicing my own Documentation-as-a-Contract (DaaC) framework.</p> <hr> <h2 id="we-have-a-name-wabe-labs">We Have a Name: Wabe Labs</h2> <p>While I have an idea that I truly believe in and know exactly the components I need to build, I have been feeling excited about this venture before starting. But one question that would keep entering my mind, <em>&ldquo;What do you tell people your business is called?&rdquo;</em></p>https://www.brettryan.dev/posts/week-two-hand-crafted-ai-advisor/Tue, 25 Aug 2026 12:58:14 +1000https://www.brettryan.dev/posts/week-two-hand-crafted-ai-advisor/<p>In my first post, I wrote about why I spent my first week writing zero business logic and instead built <strong>rig</strong> - our lightweight, POSIX-compliant local provisioning tool. It was my way of rejecting &ldquo;wiki-ops&rdquo; and applying Infrastructure-as-Code (IaC) discipline to our local environments so that a hardware failure means minutes of downtime, not a week.</p> <p>But as I transitioned into Week Two, I was hit by a different kind of operational reality check.</p>