Making it shippable
This month it stopped being a thing that only runs here.
For a long time Builder carried its own small databases off to the side: fine while it was ours alone, a problem the moment it needs to be something we can hand over. So we did the boring, necessary work. We moved everything onto one source of truth, on the platform itself, and pulled the old local machinery out entirely. We split the harness that builds from the application we actually ship, so the two are no longer tangled. And we gave it its own way to test and release itself, so it leans on nothing we do not own. It is closer now to something you could pick up and run, not just watch us run.
The change we are most taken with is a different one. This month the research stopped being something we did with a spare afternoon and became a standing part of the machine: a programme that scans for what is coming, tries things, and keeps what works. Once or twice it produced something we did not expect - working code for a way of doing a thing we had not seen done before. What we kept saying was, "we might be able to publish something with this." And then the larger thought: imagine if the research does not just make a paper, but folds back into the platform, so the next capability is not something we build by hand but something the thing comes with, that anyone holding it gets, to push their own work further than they could alone.
That is the shape of it now: a platform that studies its own field, turns what it learns into working software, and puts it in reach of whoever is holding it.
We have gone, this month, from a builder that ran in our hands to one with a single source of truth, its own path to release, and a research arm that feeds itself. It no longer feels like a project with an end. It feels like something that keeps arriving.