MathSphere Nexus
This blog is not updated casually. It is updated when something about the house itself becomes clearer — and this week, the house’s method did.
A design, however carefully written, is a claim. It says: these parts fit, this refusal happens here, this record cannot quietly change. Most houses test that claim by building the product and finding out. This house tests it earlier and cheaper: before a design is built into the product, it is built small — a prototype whose only job is to be run until its shape either holds or breaks.
A prototype here is not a sketch. To count as evidence it must pass house: its actions written to a hash-chained record, its destructive acts asking twice, its code built to the project’s discipline, and every feature tested live, with the terminal record published beside it. A sketch that fails is a sketch, and it is labeled one or left off the page.
Four designs went through that gate in two days. The floor — how one installation serves many people with no accounts: 21 of 21 checks, after a reviewer’s catch sealed an export boundary that words alone had left open. The hub — approved people and their sealed projects: 18 of 18. The broker — context carried between rooms without mixing, revocation killing every live key at once: 17 of 17. And the start lock — a voluntary password door: 26 of 26, and then proven again road by road in the owner’s own hands, down to spending a recovery key at the door and watching it die as designed.
Every one of the four was then run on a second machine — the owner’s — and agreed, count for count. Two machines, one of them the owner’s own hands: that is what proven means here, and it is a smaller word than it sounds. A prototype proves a shape. It does not prove the product, and this page never calls it one. The product builds stand in the roadmap, in their order, and each will have to earn its own proof the same way.
Three states are kept separate in this house, always: decided, built, and proven. Most disappointment in software is born from blurring them — from letting a decision sound like a delivery. The prototypes exist to keep the third word honest: when this house says a thing is proven, there is a record, a count, and a machine it ran on — and the reader is invited to check all three.
Generous software, with built-in privacy. The shape is given away freely, because a claim you cannot check is just a slogan. The rest stays home.
A command is what you type. The name is what the project is.
— Alexander