nx_motion_serve.nx

nx_motion_serve.nx -- /motion AS A TOOL, NOT A BROCHURE (2026-09-06): a visitor uploads a mesh, the sovereign auto-rig rigs it, the page shows it from three sides with its own numbers, a library clip retargets onto it, the result exports, and the operator's ACCEPT or REJECT lands from the same page. The mesh2motion-class surface, on the estate's own organs. nx_motion_serve [port] serve on LOOPBACK (default 18132); the edge proxies /motion to it nx_motion_serve emit <out.html> write the static fallback -- THE SAME RENDERER, the empty form, byte-identical SHAPE, and why (the /math pattern): plain GET and POST forms, no script, no fetch, no client runtime, so it works with JavaScript off, every job is a shareable URL, and there is no third party anywhere in the path. Routing is prefix-agnostic on purpose: the edge forwards /motion/upload and a loopback test sends /upload, and both route the same. The daemon never does the work: it types the upload by MAGIC, writes a digit-named job directory, and spawns the job organ DETACHED (double fork), so accept() is never held by a rig. It reads status rows the job writes and shows them. license_tier: ORIGINAL