nx_capcensus.nx

nx_capcensus.nx -- THE PICKED-CAP CENSUS: is a capacity bound DERIVED, or PICKED by an author? WHY THIS EXISTS, AND WHY IT IS NOT A DUPLICATE (measured 2026-08-23). The same defect class was found FOUR times in ONE session: nx_skeleton.nx SK_MAXB=32 bones / SK_MAXV=2048 verts against a corpus of 104-370 joints and 14,164-423,919 verts -- an 11.6x bone / 207x vertex overflow that made EVERY real character un-riggable, so the served worlds drew bind pose. nx_nxa_skin cluster cap 512 -> 8192, and the CAP IMPERSONATED A COUNT TWICE (clusters=510, then =2046): a saturated buffer read back as if it were a measurement. MG_CAP a SILENT input cap in the mesh path -- an oversized asset reads truncated with no announcement. nx_cron_reconcile one sys_read of 16,383 B against a 24,356 B registry: 11 production jobs silently inert, and it printed declared=55 as if that were the population. ***NAMING A MAGIC NUMBER DOES NOT MAKE IT DERIVED.*** nx_magic is the rule-11 fixer: it hoists an INLINE literal into a NAMED const, and it SKIPS const/static declaration lines BY CONSTRUCTION (its own header says so). So `const SK_MAXB: i64 = 32` is structurally invisible to it and every magic-number detector calls the file clean. Worse, its remedy MANUFACTURES this artifact: the auto-generated K_MAGIC_<value> / <PFX>_MAGIC_<value> names found in the wild (K_MAGIC_262144, K_MAGIC_65536, DC_MAGIC_131072) are picked caps wearing a constant's clothes -- THE NAME ENCODES THE VALUE, so it carries no purpose at all. That is not a defect in nx_magic (its neutrality is provable and its purpose is different); it is exactly why a SECOND, ORTHOGONAL instrument is needed. nx_magic asks "is this literal inline?". This organ asks "is this bound DERIVED or PICKED?". nx_capcliff is NOT the incumbent either: it forecasts RUNTIME growth of rostered append-only ledgers against a known reader cap. This is a STATIC census of bounds declared in source. nx_capcensus scan <dir> -> recursive classified census over every .nx under <dir> nx_capcensus selftest CLASSES (the partition MUST sum to the population, and the sum is printed): DERIVED value computed from an input size / another identifier / an expression. Healthy. PICKED a literal ceiling on data whose real size is knowable at runtime. THE WORKLIST. STRUCTURAL fixed by an external contract (syscall number, mode bits, seek whence, exit code). PROTECTIVE a bound NAMED for bounding unknowable input. See the declared limit below. UNKNOWN could not classify. Reported, NEVER folded into a known bucket. DECLARED LIMIT, so nobody reads this census as more than it is: PROTECTIVE IS UNDER-DETECTED BY CONSTRUCTION. Proving that a bound's truncation ANNOUNCES requires call-site analysis this organ does not perform; it recognises only bounds NAMED for that purpose (WINDOW/WIN/BUDGET/DEADLINE/