nx_unwired.nx

nx_unwired.nx -- FIND EVERY FUNCTION THAT IS DEFINED AND NEVER CALLED, ACROSS THE WHOLE TREE. WHY THIS IS AN ORGAN AND NOT A NOTE ----------------------------------- On 2026-08-07 I fixed a measurement leak in nx_memroot, wrote the fix, built it, deployed it, measured the "result", and recorded it in memory. `mr_body` was DEFINED AND NEVER CALLED. Two string-replacements had matched nothing and reported success. The gate was green because the gate had gone green before the tooth existed. ★★★★★★ A FUNCTION DEFINED AND NEVER CALLED IS A COMMENT. ★★★★★ A STRING REPLACE THAT MATCHES NOTHING IS A NO-OP THAT REPORTS SUCCESS -- VERIFY THE CALL SITE, NOT THE DEFINITION. The estate already had vocabulary for this failure -- BUILT+UNWIRED, "comments not code", the adoption gap -- written down in several memory files. It was written down and it still happened, three times in one session, because a law in a file is consulted at the rate advice is consulted. ★★★★★★ A LAW THAT IS ONLY WRITTEN DOWN IS ENFORCED AT THE RATE PEOPLE REMEMBER TO READ IT; THE SAME LAW COMPILED INTO A GATE IS ENFORCED EVERY TIME. FULL ECOSYSTEM SCOPE, NOT A SAMPLE: every `.nx` in the tree is both a definition source and a call source, so a helper used only by a sibling organ is correctly seen as WIRED. Reporting on one file would manufacture false positives for every library function. ★★★★★ A REACHABILITY QUESTION ASKED OF ONE FILE IS ANSWERED WRONG BY CONSTRUCTION. usage: nx_unwired [--dir D] [--quiet] exit: 0 = nothing unwired; 1 = unwired definitions exist license_tier: ORIGINAL