nx_unread_sensor.nx

nx_unread_sensor.nx -- WHICH STATUS ARTIFACTS DOES NOTHING NAME. usage: nx_unread_sensor [statusdir] default knowledge/status/ exit: 0 GREEN (single-namer count at or below its ratchet) | 1 RED (it rose) | 3 UNPROVEN See nx_unread_sensor_lib.nx for why this exists and for the blind spots it declares. In short: this estate rediscovered "a sensor nothing reads" four times in one day, and owned no instrument that could have found the fifth. Every number below is a FLOOR on readers, so a row here is a QUESTION. IT REFUSES TO RUN ON A SATURATED BOX. Composing ct_admit_now costs one small /proc read and no fork, and the alternative is a corpus-wide scan that becomes the load it was built to explain -- A DIAGNOSTIC THAT CANNOT REFUSE TO RUN IS A LOAD GENERATOR WITH GOOD INTENTIONS. THE RATCHET SELF-BASELINES ON FIRST SIGHT, so shipping it cannot turn every build red on day one, and it is written ONLY on a fall or a first run: a ratchet that rewrites its baseline on a RISE launders itself green and is worse than no ratchet at all. license_tier: ORIGINAL expect_exit: 0 Read-only. No hw writes (Rule 26).