nx_selfsuff_gate.nx

nx_selfsuff_gate.nx -- the referee for the SOVEREIGNTY LEDGER (nx_selfsuff) and for the ranker term it feeds (nx_compare_rank rk_selfsuff_term, PR11). THE TOOTH THAT MATTERS IS THE POSITIVE CONTROL. A dependency penalty that fires on EVERY rung passes every negative test ever written for it -- it demotes the bad rungs, and nobody notices it demoted the good ones too, because a uniform multiplier is a no-op on ORDERING wearing the costume of rigour. So the first tooth here is an IDENTITY: with a ledger that says zero dependency, the ranked priorities must be BYTE-FOR-BYTE the same sequence as with no ledger at all. Fixtures live under /tmp/<gate>/ (a gate must not share its fixture with a production beat), except the fixture DOMAIN, which must sit beside the real compare data because nx_compare_rank resolves buildroot/knowledge/compare/<dom> itself. It is named _ssgatefix so it is unmistakable, it is in no regen/radar list so no generator consumes it, and it deliberately carries NO ver| ladder so the ranker files NOTHING into the production pm intake journal on a gate run. END-TO-END: this gate fork/execs the DEPLOYED ./nx_selfsuff.elf and ./nx_compare_rank.elf, so nx_gate_bite needs its 4th argument (subject target) or every mutant survives by construction.