nx_ladder_lib.nx

nx_ladder_lib.nx -- THE ONE RULER FOR A BOARD'S LADDER TO SOTA: every rung says what it is FOR, and the board says what best-in-class and the frontier ARE, dated. Operator 2026-09-06, after a day spent climbing toward a 2014 bar: "how you framed it here is how all the /compare domains should be emitting with clarity on what dependencies from the first byte up all grow us each rung up to sota with a clear target on what is best in class and what is frontier." The framing that answered "how much of the 2014 work applies to the 2026 stuff" was a role per rung (the ruler and the syntax tools are SUBSTRATE the frontier itself uses; the perceptron is a triangulation ARM, not the contender; the target was SUPERSEDED) against two named, dated targets. This lib makes that framing DATA every board carries and every consumer reads, instead of prose one seat wrote once. THE DATA (rows in <domain>.plan, pipe-separated, NO pipe inside a field): sotatarget|<id>|<class>|<sotabar-id>|<statement>|<ref key> class is best-in-class (the proven, deployed leader today) or frontier (the research edge, current month); <sotabar-id> names the sotabar| row that DATES it (nx_barfresh_lib judges that month), so a target without a bar is UNDATED -- the exact defect that cost the day. rungrole|<rung-id>|<role>|<target-id>|<why> role is substrate (infrastructure the target's own methods consume: data, rulers, syntax tools, arithmetic), arm (a sovereign arm that triangulates or baselines the target without competing for its number), contender (a rung whose done-rule is a number against the target's) or superseded (kept as capability, retired as a claim). Dependencies come from the rung| row's own deps field; this row adds the DIRECTION. THE STATES: per target DATED (its bar row exists), UNDATED, BADCLASS, DUPLICATE (its id an earlier sotatarget row already carries: one target declared twice); per rung PLACED, UNPLACED (no rungrole row), BADROLE, BADTARGET (its rungrole row names a target no sotatarget row declares); rungrole rows naming no rung are ORPHANS, and a rungrole row for a rung an earlier rungrole row already placed is a DUPLICATE ROLE (counted apart from orphans, refused alike). MEASURED 2026-09-14 on search.plan: two sotatarget rows for one bar and one rung id used twice landed across a transport drop, and only the rung id was refused (the plan-graph rule); ld_refusal_rule names WHICH rule refused so a consumer prints it from this lib instead of paraphrasing. THE VERDICT: NO-LADDER (exit 3) when the plan declares no target rows -- a domain opts in by declaring its first target and is LABELED until then, never refused; LADDERED (exit 0) when both classes are declared and dated and every rung is placed; PARTIAL (exit 1) otherwise, with every offender named -- a half-declared ladder is the "12-year-old tech" shape (a target without a month, a rung with no direction), so once a board opts in it is held to the whole contract. COMPOSES nx_barfresh_lib's line and field readers (one parser for plan rows) and its sotabar tag; classifies only. license_tier: ORIGINAL No hw writes (Rule 26).