nx_math_serve.nx

nx_math_serve.nx -- /math AS A TOOL, NOT A BROCHURE. WHY THIS EXISTS. The operator asked for a UI where you can DO mathematics; what shipped first was a page whose formulas were typeset at publish time and whose worked solutions were three hardcoded equations. Their words: "/math is just static output how does that match what i asked for". It did not. A page that DEMONSTRATES a capability is a different artifact from one that PROVIDES it, and only the second is a UI. WHAT MAKES IT INTERACTIVE, AND WHY THIS SHAPE. A visitor types an equation into a PLAIN GET FORM. There is no script, no fetch and no client runtime: the estate's document portal reached the same conclusion (portal actions as plain forms), and a GET form has three properties a script cannot match here -- it works with JavaScript off, every solved equation gets a SHAREABLE URL a teacher can hand to a class, and there is no third-party anything in the path. ONE RENDERER, TWO ENTRY POINTS. This daemon calls mp_render from nx_math_page, the SAME function the static build calls. Two renderers for one surface is the duplicate-ruler defect wearing HTML, and it would drift the moment either was edited. The static file remains as the fallback a reader gets if this daemon is down, and it is byte-identical to what this serves for an empty form. ⚠BINDS LOOPBACK, DELIBERATELY. A daemon binding INADDR_ANY is on the LAN the instant it starts; the estate has measured that. The edge proxies to it, so it is never directly exposed. license_tier: ORIGINAL