nx_research_river.nx

nx_research_river.nx -- EMIT ONE AREA'S RESEARCH INDEX FROM THE REGISTRY. The ocean (/wiki/research) has been generated from the `resbrief-` plane since 2026-08-01, but every RIVER -- /code/research, /product/research -- was still a HAND-EDITED page. On 2026-08-02 that bill came due twice, in OPPOSITE directions: * the HAND page was STALE: three briefs published that day were registered and rendered into the ocean, while /code/research (the page a reader of the code wiki actually lands on) still listed the older set and knew nothing about them; * the REGISTRY was WRONG: five briefs whose pages had been written and were being served (research_agentmem, research_codequality, research_perfmath, research_modeltier, research_foodchem) still carried status=STUB and, in the slug column, their CORPUS SOURCE FILENAME rather than their served page name. The ocean therefore rendered five live briefs as unlinked corpus-only stubs. THE LAW THIS ORGAN IS BUILT AROUND: A GENERATED INDEX INHERITS ITS REGISTRY'S ERRORS AND LAUNDERS THEM AS AUTHORITY. Generation does not create truth; it propagates whatever the registry says, at machine speed and with a machine's air of correctness. Replacing a hand-edited index with a generated one is only an improvement AFTER the registry is proven a superset of the page it replaces -- which is why the five rows above were repaired against the filesystem (the oracle for what is actually served) BEFORE this organ was allowed to overwrite anything. nx_research_river <area> -- writes sites/nishifamily/<area>/research.html Sections are the DISTINCT STATUS values in first-seen order, exactly as the ocean sections by distinct AREA. A new status appears by adding a plane row -- no organ edit. That is what recovers the hand page's Published / Maps / In-progress grouping without hardcoding a status list that would silently drop any status nobody thought of. Reads with sts_load_honest, NEVER plain sts_load: a stale declared count silently truncates the plain loader, and an index that under-reports its own library is indistinguishable from a complete one. Declared / loaded / in-area / rendered / beyond are printed AND rendered on the page, so a READER can see partial coverage, not just whoever ran the organ. Plane row (8 col): id area slug title date status forks_off scope license_tier: ORIGINAL No hw writes (Rule 26). expect_exit: 0