nx_civicmap_gate.nx

nx_civicmap_gate.nx -- GATE for the civic quality-of-life map: CM1 admission, CM2 county join, CM3 the honest choropleth. Subject: nx_civicmap_lib.nx, imported and exercised IN-PROCESS, so this gate can never report on a stale deployed artifact instead of the source it names. WHAT THIS GATE IS ACTUALLY FOR. The easy version of every one of these teeth is vacuous: * A deny-suite alone proves nothing -- ★A GUARD THAT REFUSES EVERYTHING PASSES EVERY NEGATIVE TEST. So the first tooth is a POSITIVE control (a complete row MUST be admitted) and every refusal tooth asserts WHICH RULE FIRED, not merely that something was refused. * "The map rendered" proves nothing about honesty. The load-bearing tooth is ARITHMETIC: the number of data-value attributes in the emitted page must EQUAL the number of PRESENT counties. An implementation that painted suppressed counties with the bottom bucket still renders, still looks like a map, and fails that count. That is the tooth the trivial wrong version cannot pass. * Every fixture is built HERE, at runtime, under /tmp/nx_civicmap_gate/ -- never in knowledge/store, because a gate that shares a fixture with a production beat measures the beat's races and reports them as the subject's defects. Preconditions use gv_need, so "I could not write my own fixture" ends SKIP and never RED: a gate that reports a broken environment in the same word as a broken subject teaches everyone to ignore it. license_tier: ORIGINAL No hardware writes (Rule 26).