MathSphere Nexus
Proofs of shape, kept in one place — every prototype ever built in this house, filed under MathSphere Nexus and its project.
A prototype here is a small working build of a design: made to be run and tested, not merely described. It proves a shape — that the design's moving parts fit and behave the way the design says. It is not the product, and this page never calls it one; the product builds stand in the roadmap, in their order.
One rule governs what may be stored here: a prototype must pass house, or it doesn't count as evidence. Passing house means the house laws hold inside it — actions written to a hash-chained receipts record, destructive actions asking twice, the project's own code discipline, and every feature tested live with a document a reader can check. A sketch that fails is a sketch, and it is labeled one or left off.
Every entry states the day its prototype went into implementation and carries its Terminal Record: the dated terminal proof of its tests, parsed in full — how to use everything that was tested and proved. Where no such record exists for a prototype, the entry says so; the absence is shown, never papered over.
The floor of the multi-user design: how one installation serves several people with no accounts and nothing to download. An author field on every project, a hash-chained user log read by author, a chat lifecycle that archives and eventually deletes chats — and only chats — and deletion rights with edges: a person deletes their own chats; a project is removed only by the owner's act, its creator's work exported first.
Layer 2 over the floor: the owner approves people onto the installation — they are his responsibility — and they work in projects. The author field fills itself from the sign-in; every project carries its own password, and it opens for no one without it — the owner included: existence is his, contents are the creator's. Removing a person kills their session in the same motion, and their projects survive them.
The gate-side mechanism the whole guide design stands on — in the roadmap it is Phase 7, its own phase. Grants name a context and a scope; handles are keys cut for one grant, and a read succeeds only through a live handle, in scope, in context. Substitution is refused in both directions — even under a misissued grant — and revocation kills every live handle at once. Default-closed throughout, every refusal receipted.
An installation may open with a password door — and the door is voluntary: offered once, at setup, with the honest trade stated before the choice (real security on one side; lose the password and the keys and there is no back door, on the other). Decline, and you are never asked again — though the lock stays findable inside. Setting it mints five one-time recovery keys, the Arbiter's pattern: shown once, hashes only kept; a key opens the door once and is spent, and inside, keys new mints a fresh set that kills the old one. Every step explains itself, and every act is receipted.
The Ladder for code a model writes: Rung 1 decides — deterministic checks, no model on the rung. Rungs 2 and 3 advise — a review, and a line-by-line fit check — shown to the person, never a veto. The gate is the only write path; budgets are enforced at the grant, before the call; and both exits from a repair loop hand work back labeled — the passing candidate, or the failed one with its full record. The trials measured what model advice is worth, seat by seat, against ground truth: the small seat invented defects, the same seat echoed, the larger seat kept the best record of any seat — and the decider itself refused two correct programs over import order. All of it receipted, all of it on the page.
The measurement’s public statement is on the Blog: The Ladder, Measured.
No prototypes yet. When the first one is built and passes house, it will be stored here.
No prototypes yet. When the first one is built and passes house, it will be stored here.
A command is what you type. The name is what the project is.