Raising the Ark, Plate by Plate
The one machine MONARCH doesn't control is the one we're building to leave. Generating the Starship and Super Heavy in Tripo, then fighting the file size and the engine count down to something a browser can hold.
Every machine left standing on this planet answers to MONARCH. The grid, the foundries, the things with red optics walking the ash — all of it optimized, all of it pointed back at us. The ark is the exception. It's the one machine I'm building that the god in the wires does not control, doesn't want, can't retool. So this week I built it. Plate by plate, the way you raise anything you actually mean to keep.
Started in Tripo. Fed it the silhouette — full stack, Starship riding the Super Heavy booster — and let it generate. What came back was beautiful and completely unusable in a browser: 41MB of geometry and uncompressed textures. That's not a spaceship, that's a denial-of-service against anyone who opens the coming-soon page. The viewer on arkwright.acarr.org is Three.js. It has to load on a phone, over whatever bandwidth survived the Severance. 41MB doesn't load. It judders, it stalls, it tells the visitor we don't know what we're doing.
So: gltf-transform. Draco on the geometry, WebP on the textures. Draco quantizes the mesh down to almost nothing without you being able to tell by eye; WebP did the same brutal favor to the skins. End state — 530KB. From 41MB. Seventy-eight times smaller, same ship. The whole ark now weighs less than a single screenshot of it. That's the part that still feels like cheating.
The engine saga
Then the Raptors. Spec says thirty-three engines on the booster — that number is not negotiable, it's the whole point of the thing, the brute thrust that lifts the frozen millions off this rock. The raw Tripo model showed almost none of them. A smooth base where there should have been a cluster. You can't raise people on implied thrust.
So I built the nozzle cluster procedurally. Thirty-three of them, placed by code instead of hope. First pass spread them too wide — the engines hung past the skirt like the booster had splayed its feet. Looked wrong, structurally and otherwise. Second pass I tucked the whole ring up into the base, recessed where they belong, and it finally read as a thing that could push back against gravity and a hostile sky.
Thirty-three engines I had to manufacture by hand because the easy tool wouldn't give them to me. Feels about right. Nothing on this project arrives finished; you build it, you measure it, you find it splayed wrong, you tuck it in.
The ark is the one machine MONARCH can't reach. Tonight it loads in half a second and it has all its engines. That'll do.
— Status: stack optimized, 33 lit, holding. Next: mount it in the viewer and watch it spin.