nx_skelgen.nx

nx_skelgen.nx -- PIPELINE STAGE 1: SKELETAL GENERATION with JOINT CONSTRAINTS. The industry's first stage is "algorithms define bone lengths and joint constraints from height and proportion parameters". An audit of our stack found stage 1 PARTIAL: a rig existed but ran on BORROWED scanned bones, and nothing generated lengths from parameters or constrained a joint at all. ★WHAT ALREADY EXISTED, AND WHY THIS DOES NOT DUPLICATE IT: runtime/nx_skeleton.nx is a skeleton + linear blend skinning system -- bones as data rows {parent, local offset, yaw, pitch}, world pose by parent composition, all integer. That is a rig FORMAT and a poser. It does not GENERATE lengths from anthropometry and it has no joint limits. This organ produces what that one consumes: generated bone rows plus the constraint table the pipeline requires. Compose, do not reimplement. ★JOINT CONSTRAINTS ARE THE POINT, and they are fail-closed. A knee that can bend backwards is not a skeleton, it is a bag of segments. Every joint carries an anatomical range, and a pose outside it is REFUSED rather than clamped silently -- because a silently clamped pose looks like a working animation while lying about what the body did. nx_skelgen <out.dat> [stature_mm] [sex 0-1000] [seed] nx_skelgen check <joint_index> <angle_deg> -> is this pose anatomically legal nx_skelgen selftest license_tier: ORIGINAL expect_exit: 0 No hw writes (Rule 26).