nx_machine_graph.nx

nx_machine_graph.nx -- data-driven printer description: build volume, kinematics, motion envelope, thermal limits, hardware geometry. No magic numbers anywhere in the slicer (Cardinal 11) -- every printer-specific value lives here, parameterized. Per cardinal NISHI_3D_PRINT_ROADMAP §2.8 + bits-up-exceed axis "cross-printer profiles don't port": adding a new printer to the substrate's slicer is DESCRIBING its NxMachineGraph, NOT rewriting any slicer code. This is the architecture promise that makes P6/P7 multi-printer proofs achievable, not aspirational. Distinct from nx_motion.nx (which is Lucas-Kanade optical flow for video -- totally different concept; printer "motion" here is the kinematic envelope, not frame-to-frame estimation). Unit conventions per field (documented at struct definition): - Build volume in integer millimetres (no sub-mm precision needed) - Nozzle / filament diameter in integer micrometres - Velocities in integer mm/s - Accelerations in integer mm/s² - Temperatures in integer °C - Q14 fixed-point only where ratios are needed (none here yet) Why mixed integer units rather than uniform Q14: Real-world printer specs are quoted in mm/s, mm/s², °C -- the integer units match operator + manufacturer conventions. Slicer composes nx_fp32_q14 + nx_machine_graph at code points where it needs cross-unit math, with explicit conversion. Operator-verified defaults: nx_machine_graph_qidi_xmax3() returns values verified 2026-05-19 against official Qidi US store specs. Operators MUST verify against their actual unit before any real print -- printer-to-printer variance exists even within model. license_tier: ORIGINAL