Built, run,
learned from.

The hard part

Real geometry isn't computed in the browser but on the server, in FreeCAD and OpenSCAD. Every slider move still has to show something instantly. So the preview renders client-side in Three.js, while the authoritative file is rendered server-side. Two geometry pipelines that have to agree.

The hard part

A language model allowed to write files is a language model that breaks files. No tool touches the data directly: every one returns a change proposal that only runs after confirmation. Proposed checkboxes are checked against the real file beforehand and dropped if the text doesn't exist exactly. That's where invented tasks get filtered out.

The hard part

Models know what a chair looks like, but not how tall it is. Without a detour through a search for real dimensions, parts come out at completely the wrong scale, technically flawless and practically useless.

The hard part

The GPU sits behind a home connection with no fixed IP. Instead of an incoming port, the worker fetches its own jobs: outbound connections only, no open port, no reverse proxy, no port forwarding on the home router.

The hard part

Four gigabytes of RAM for the shop, the database, two CAD services, a knowledge base with its own embedding model, and a mail server. Every service has a hard memory limit, otherwise one grabs everything and the rest dies with it. No single port is open to the outside; all traffic runs through an outbound tunnel.