<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>cland build log</title><description>How cland is built by its own crew: what each release took, what it cost, what broke and what we changed.</description><link>https://cland.app/</link><language>en</language><item><title>v0.3.1: a fifth of the memory, and no silent Coordinator</title><link>https://cland.app/log/v0-3-1-a-fifth-of-the-memory/</link><guid isPermaLink="true">https://cland.app/log/v0-3-1-a-fifth-of-the-memory/</guid><description>v0.3.1 cuts the cland hub to about a fifth of its memory on our own project and makes sure a message to the Coordinator never silently goes undelivered. 25.5 hours from a voice note to the release, steered from a phone.</description><pubDate>Sat, 31 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>memory</category><category>reliability</category></item><item><title>v0.3: the crew in your Telegram and Discord</title><link>https://cland.app/log/v0-3-the-crew-on-your-phone/</link><guid isPermaLink="true">https://cland.app/log/v0-3-the-crew-on-your-phone/</guid><description>v0.3.0 lets you follow and steer an AI coding crew from Telegram or Discord: General both ways, asks and approvals as cards, voice notes as answers. Seven epics, every demo clear on its first run, and a live run on real bots that found the bugs the fakes could not.</description><pubDate>Fri, 30 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>remote</category><category>telegram</category><category>discord</category></item><item><title>v0.2 and v0.2.1: the crew moved into the browser, and a free model landed six tasks in a row</title><link>https://cland.app/log/v0-2-the-browser-and-a-free-model/</link><guid isPermaLink="true">https://cland.app/log/v0-2-the-browser-and-a-free-model/</guid><description>v0.2 put the whole workbench in the browser and on the phone: 12 epics, every demo clear on its first verdict. v0.2.1 then ran a free model in every crew role on real tasks. It landed its work with no model-caused rescue. What failed was our ability to prove it.</description><pubDate>Sun, 25 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>web</category><category>opencode</category><category>models</category></item><item><title>v0.1.4: the wait for tests fell to a tenth, and the release eve took five runs</title><link>https://cland.app/log/v0-1-4-a-tenth-of-the-wait/</link><guid isPermaLink="true">https://cland.app/log/v0-1-4-a-tenth-of-the-wait/</guid><description>A merge queue and test tiers cut the time tasks spent waiting for tests from 21% of test time to under 10%, and the crew landed 315 tasks in 91 hours. The night before the release still took five runs and eight hours, and not one of the red runs was a product bug.</description><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>verification</category><category>merge-queue</category><category>onboarding</category></item><item><title>Why the test suite ate the crew: 97% of its time boots real processes</title><link>https://cland.app/log/why-the-suite-eats-the-crew/</link><guid isPermaLink="true">https://cland.app/log/why-the-suite-eats-the-crew/</guid><description>We read all 237 test files and 557 run receipts to find out why verification set the crew&apos;s pace. The suite is not too big. It runs at the wrong level, and the fix is test tiers enforced by the hub plus a merge queue.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><category>verification</category><category>testing</category><category>study</category></item><item><title>v0.1.3: twice the pace, and none of seven stage-close runs went green</title><link>https://cland.app/log/v0-1-3-twice-the-pace/</link><guid isPermaLink="true">https://cland.app/log/v0-1-3-twice-the-pace/</guid><description>The crew merged 2.9 tasks an hour instead of 1.2, and more of them cleared review on the first pass. The test suite did not keep up: the queue shrank, but each run got longer, droplets cost $18.11, and the release took nine runs.</description><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>verification</category><category>executors</category><category>rules</category></item><item><title>v0.1.2: the crew spent twice as long waiting for tests as running them</title><link>https://cland.app/log/v0-1-2-waiting-on-the-suite/</link><guid isPermaLink="true">https://cland.app/log/v0-1-2-waiting-on-the-suite/</guid><description>In 77 hours a cland crew landed 94 tasks across 10 epics for $1.17 of cloud runners. The crew was not the bottleneck: the verification queue was, and not one red integrated run found a product bug.</description><pubDate>Thu, 15 Oct 2026 00:00:00 GMT</pubDate><category>retrospective</category><category>verification</category><category>executors</category></item></channel></rss>