nx_infinigen_page.nx

nx_infinigen_page.nx -- THE PROCGEN VALIDATION SURFACE (/infinigen, operator 2026-08-27: "give us a nishifamily.com/infinigen ui so i can validate you are generating procgen and not cheating with hand crafting"). The proof this page publishes is MECHANICAL, not narrative: 1. it IMPORTS the shipping engine and REGENERATES every recipe world in-process at emit time -- every number below is measured from freshly generated voxels, never transcribed; 2. every world is generated TWICE into two arenas and the voxel-fold fingerprints must be EQUAL (same seed + same rows = the identical world, every time) or the emit REFUSES; 3. the effective generation parameters print with PROVENANCE per row -- identity default vs recipe override vs derived -- read back from the spec table the generator consumed; 4. the served world pages carry ZERO voxel data (each world materializes in the visitor's browser from the seed + the rows shown here), and beach-vs-isle is the standing seed experiment: ONE identity, two seeds, two different measured worlds. House law: this page is EMITTED from data (knowledge/world_recipes.conf + the engine). Recipe parsing here is a scoped 4-field TSV read; the full parser (gpe_recipes_load) lives in nx_game_page_emit and is deliberately NOT imported: that lib is a sibling lane's actively edited file and this organ needs name/vnum/seed/title/spec only. Declared imprecision. usage: nx_infinigen_page (runs from nishihost cwd like every registered tool) exit: 0 SHIPPED | 5 page-fault (too small / determinism REFUSED) | 6 deploy | 7 readback | 8 recipe-malformed-or-unreadable license_tier: ORIGINAL No hw writes (Rule 26).