nx_unread_sensor_lib.nx

nx_unread_sensor_lib.nx -- the pure core of the UNREAD-SENSOR census. THE PATTERN THIS EXISTS FOR, MEASURED FOUR TIMES IN ONE DAY (2026-09-03): * procchurn.jrnl carried a correct sev= on every frame for 35 DAYS and no organ read that field. * nx_raidwatch was verdict=RED the whole time and nothing consumed it. * loadgov LV1 was the same shape one board over. * nx_health reported overall:OK for 16 services while having NO STORAGE AXIS AT ALL, and nx_healthtruth -- built for exactly that shape -- had been STAGED and never promoted. Four independent rediscoveries of one shape is not four mistakes, it is A STRUCTURAL PATTERN WITH A MEASURED RECURRENCE RATE, and the estate had no instrument for it. A SENSOR WHOSE OUTPUT NOTHING READS CANNOT CHANGE AN OUTCOME, AND FROM ANY DASHBOARD IT IS INDISTINGUISHABLE FROM ONE THAT IS WORKING. WHAT IT MEASURES, STATED AS THE NARROW THING IT IS. For every artifact under knowledge/status/, it counts how many DISTINCT .nx sources mention that filename literally. That count is a FLOOR on readers and writers together, so the buckets are named for what was measured and never for the remedy: NO-LITERAL-REFERENCE no source names it at all -- built from a variable, or genuinely orphaned SINGLE-NAMER exactly one source names it, which is almost always its own producer NAMED-BY-SEVERAL at least two, so something other than the writer can see it SINGLE-NAMER is the suspicious class, NOT a proven defect: a producer that also re-reads its own file is legitimately single. ★ NAME A BUCKET FOR WHAT WAS MEASURED, NEVER FOR THE ACTION YOU IMAGINE FOLLOWS -- a bucket called UNREAD would send the next reader deleting live instruments. DECLARED BLIND SPOTS, because a census that hides its own reach is worse than none: * only .nx sources are scanned. A consumer that names a status file from a .conf, a cron row or a shell fragment is INVISIBLE here, so a SINGLE-NAMER row is a QUESTION, not a verdict. * a path assembled at runtime from a prefix and a variable is invisible by construction. * a file read past the per-file cap contributes only its head, and those files are COUNTED.