nx_favela_decay.nx

nx_favela_decay.nx -- the TIME DIMENSION on the favela census (operator 2026-07-20: "are landmines getting eaten along with all of our debt"). MEASURED ANSWER THAT MOTIVATED IT: favela rooted_permil=94 vs debt eaten 490permil -- landmines get ROOTED ~5x slower than debt gets eaten. ROOT ASYMMETRY: "mitigated" is a TERMINAL state in the 7-field favela manifest (there is NO time field at all) and it earns HALF CREDIT FOREVER. A mitigation here is overwhelmingly "a WARNING line in MEMORY.md", so tribal knowledge is a load-bearing safety mechanism -- exactly what rule 26 forbids ("proven mechanically, never asserted"). THIS ORGAN GIVES A MITIGATION AN EXPIRY. Data-driven per rule 11: the decay window is a CONFIG ROW in the ledger, NEVER a constant in code. Evidence-derived per the R2b law: age comes from an APPEND-ONLY ledger of observations, never from prose and never from an assertion. FAIL-CLOSED: a missing/unreadable config measures decay_days=0 => every mitigation is ALREADY expired => maximally loud. A missing config can never silently grant infinite grace. HONEST: the clock starts at FIRST OBSERVATION, not at the true mitigation date (unknowable -- no historical record exists); the output DECLARES this rather than faking a backdate. COMPOSES, DOES NOT DUPLICATE (board queried before building, 2026-07-20): cap-autonomy owns auto-filing to intake/debt/frontier -- this organ EMITS the DECAYED signal and THAT lane files it. ws-intel8 owns nx_feeder gap-derivation. tsv-to-native-planes owns the favela_classes.tsv migration, so this adds NO TSV: the ledger is an append-only evidence log (the ws_sync.jrnl / token_efficiency.log pattern), conflict-free under concurrent seats via O_APPEND. VERBS: check (default -- auto-stamps then evaluates) | stamp | config <days> | selftest license_tier: ORIGINAL expect_exit: 0