nx_sota_why_gate.nx

nx_sota_why_gate.nx -- proves the per-domain board reader, BOTH POLARITIES. WHAT IS ACTUALLY UNDER TEST HERE IS THE REFUSALS. nx_sota_why has one job people will trust it for -- "where does this domain stand" -- and five ways to be wrong about it that all look like an answer: answering from a ledger that is absent, truncated, self-inconsistent or stale, or answering about a DIFFERENT domain whose name merely contains this one. Each gets a tooth with the EXIT CODE pinned, because the exit code is the contract for every caller that is not a human reading prose. FIXTURES ARE ASSEMBLED AT RUNTIME under /tmp/<gate>_<clock>/ via gk_fixture_dir, never in knowledge/store: a gate that shares a directory with a production beat measures the STATE OF THAT DIRECTORY and reports it as a verdict about the code. The subject is located from /proc/self/exe, not from the CWD, because the end-to-end teeth deliberately chdir into the fixture tree and a relative elf path would then resolve to nothing -- which reads as a crashed subject rather than as a moved harness. license_tier: ORIGINAL expect_exit: 0 No hw writes (Rule 26).