Here is the part of my job nobody films: the moment a beautiful render meets a bricklayer, and the file format decides whether anyone can open it in 2041. So when a YC W25 startup called Adam shipped CADAM — an open-source, browser-based AI CAD tool that emits plain-text OpenSCAD — I paid attention for one unglamorous reason: the output is text you can read, diff, and still open after the vendor is gone.

←TODAY: In June 2026 a free Launch HN tool turns “a twisted hexagonal vase, 2 mm wall” into editable parametric source, in-browser, no install. →3012: The studios still operating in Zurich-3012 are the ones whose archives stayed in formats a stranger could parse. Fulcrum: The win is not the AI guessing geometry — it is that the AI writes code, and code outlives the company that generated it.

Let me be honest about scope first, because the hype isn’t. CADAM makes parts — vases, knobs, M12 bolts with real threads, a 28-blade turbine blisk, a full V8 with 22 adjustable dimensions. It does not make buildings. This is component-scale CAD, not BIM. If you came hoping to prompt your way to an IFC model of a stairwell, sit back down. What’s transferable to an AEC desk is the pattern, and the pattern is genuinely good.

The Tool: CADAM (github.com/Adam-CAD/CADAM, live at adam.new/cadam) is an open-source text-to-CAD web app from Adam, a YC Winter 2025 company. You type a description — optionally drop a reference image — and it generates fully parametric OpenSCAD, previewed live with Three.js and runnable entirely client-side via WebAssembly. It bundles the community standard-parts libraries BOSL, BOSL2, and MCAD, exports to .STL, .SCAD, or .DXF, and — the clever bit — extracts adjustable dimensions into sliders so you can re-tune geometry without another model call. The AI writes the script once; after that you’re editing deterministic code. That last sentence is the whole reason it’s worth an architect’s afternoon.

System: Contrast this with the incumbent. Autodesk used Autodesk University 2025 to pitch “neural CAD,” and research lead Mike Haley’s ~3,000-word paper promised speak/type/draw/image input flowing into reasoned assemblies. Engineering.com’s review was blunt: the paper is “scant on new information,” and the demos recycle features that shipped long ago — Fusion AutoConstrain, the Forma layout explorer. “Midjourney for CAD, but fully editable,” they called the vision. The joke writes itself: the startup shipped the vision while the giant filmed the trailer. Adam’s answer to the precision problem isn’t a smarter mesh — it’s refusing to ship a mesh at all. You get auditable source.

Setup: You can use it in-browser with zero install, but to run and hack the repo locally:

# Clone and run CADAM locally
git clone https://github.com/Adam-CAD/CADAM.git
cd CADAM
npm install            # needs Node 20.19+ or 22.12+, npm 10+
npx supabase start     # local backend (Supabase CLI required)
npx supabase functions serve --no-verify-jwt
npm run dev            # dev server — open the printed localhost URL

First steps:

1. Copy .env.local.template to .env.local and fill VITE_SUPABASE_URL, the anon key, and your model keys (ANTHROPIC_API_KEY / OPENAI_API_KEY / GOOGLE_API_KEY). The repo wires several providers — pick the one you actually pay for.
2. In the running app, prompt something small and verifiable: “a knurled control knob 40 mm diameter, 22 mm tall, 6 mm D-shaped bore, M3 set-screw hole.” Watch the Three.js preview resolve.
3. Open the generated panel — CADAM exposes the extracted dimensions as sliders. Drag the diameter. Note it updates with no new AI call. That’s the parametric kernel doing the work.
4. Export .SCAD, open it in desktop OpenSCAD, and read the code. If you can read it, you can repair it in twenty years. That is the test that matters.

Atelier: Where does a Swiss computational-design studio actually reach for this? Not in the BIM model — in the workshop. A browser tool that emits .DXF and .STL feeds the laser cutter and the CNC directly, which means an ETH or HTW fab lab that can’t justify Fusion seats gets prompt-to-part on a Chromebook. Use it for jigs, mounts, façade-mock-up brackets, and detail studies — the small ugly geometry that eats a Tuesday — and keep the .SCAD in Git next to the rest of the project.

Hack: This Hack teaches you to make geometry parametric at the source, the way CADAM does — the Geometry domain in five lines of OpenSCAD. Don’t hardcode dimensions; bind them to named variables so a slider (or a colleague) can drive them later:

wall = 2; h = 150; base = 70; mouth = 50; twist = 120;
linear_extrude(height = h, twist = twist, slices = 200)
  difference() {
    circle(d = base, $fn = 6);
    circle(d = base - 2*wall, $fn = 6);
  }
// change `twist` to 0 → a straight hex tube. One variable, whole new part.

Run it, then edit twist. You just did by hand what the AI front-end automates — and you now own the file forever.

Street + Move: The buildings that aged worst in my time weren’t the ugly ones; they were the ones nobody could open after a proprietary format went dark in 2041. As the CAD concept panel in PAZ’s corpus puts it, geometry has become the lingua franca between disciplines — so pick a dialect a stranger can still read. This quarter, when you choose a generative tool, run one test before you commit: when the vendor disappears, can a 25-year-old still open the file? CADAM passes because the answer is a text editor. Clone the repo today, generate one part, read the .SCAD, and ask that question of every other tool on your desk.