The concept
Nightprint draws software architecture as machines: a Next.js site renders published machines in the browser from an engine, a 3D scene and a UI kit that share design tokens.
The project has three zones, read left to right. Readers hold the visitor's browser, a search crawler or a link-preview fetcher; they reach the site only through the web app's pages and image endpoints. The delivery zone holds the code that turns a machine into a page: the Next.js app, the site views, the 3D scene, the UI kit and the film package.
The core zone holds what the rest depends on: the engine, which defines the machine format and plays it; the design tokens; and the catalogue of published machines, which is written with the engine's definition function.
The imports keep one rule: they point inward, from delivery to core, and not back. The engine imports only zod. The UI kit imports the tokens and no engine code, and the site views are the seam that turns the engine's snapshot into the plain props the UI kit takes.
The web app builds its pages once, at build time, into static files; the browser then runs the stage. Each step of a machine moves a token along a route, and the two what-if switches show what would break if an import crossed a boundary the code keeps today.