nx_magicname.nx

nx_magicname.nx -- THE MEANINGLESS-NAME DETECTOR, and the ratchet that keeps the number falling. THE DEFECT IT MEASURES, stated plainly: the estate's own rule-11 remedy manufactures the disease. nx_law_warden counts BARE LITERALS and nx_magic apply hoists them to a named const -- but it names them X_MAGIC_<value>, which restates the number instead of saying what it MEANS. The ratchet then reads GREEN while the code is no more legible than before: a magic number wearing a costume, and harder to grep for because it no longer looks like a literal. Measured cases from one afternoon: BG_MAGIC_40500 was hiding BHASKARA I'S SINE APPROXIMATION; AS_MAGIC_73856093/19349663/83492791 were hiding the TESCHNER 2003 spatial-hash primes; AS_MAGIC_8388607 was an IEEE-754 mantissa mask sharing its value with an unrelated triangle cap. In every case the value was right and the NAME was the defect. THE RULE, mechanical and unarguable: a const whose identifier contains _MAGIC_ followed only by digits is named for its value. That is decidable from the identifier alone -- no heuristic, no threshold, no sample. RATCHET: knowledge/status/magicname.conf holds the agreed ceiling. The count may FALL freely; a RISE is refused. First run with no conf SEEDS it and says so, rather than inventing a floor and calling it a pass. It NAMES every offender it counts -- a count without a worklist is not actionable (banked law). nx_magicname [dir1] [dir2] default: runtime/_hdl_build and runtime license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0