nx_leaderboard_lib.nx

nx_leaderboard_lib.nx -- THE ONE reader of <dom>.leaderboard (ecosystem EC44, 2026-09-15): leaderboard rows AS DATA, read from mirrored bytes, with the estate's own row placed by arithmetic, never by hand. WHY. The operator's goal names a public leaderboard (BRIGHT) as the evidence surface, and the estate's measuring organ (nx_beir_eval be_bright) already writes the estate's row into knowledge/compare/<dom>.leaderboard -- but no compare page rendered the file, so the number lived in a file nobody published. A LEADERBOARD THE BOARD DOES NOT RENDER IS A CLAIM THE BOARD CANNOT MAKE. This lib is the ruler the emitter's lb_pass projects: head|<board>|<source url>|<mirror>|<pin>|<fetched YYYY-MM-DD>|<metric> lb|<board>|<rank>|<system>|<org>|<score>|<date>|<entry url> A score is decimal with at most one fractional digit (the published boards print nDCG x 100 to one decimal); it is held as score x10 so 66.9 and 14.5 compare as integers. The ESTATE's rows are the ones whose system starts with LB_ESTATE_PREFIX; every other row is a published rival. The estate's RANK is 1 + the number of rival rows whose score is strictly higher (a tie ranks with the tied); its GAP is the leader's score minus its own; its LEAPS are the score deltas between its own rows in date order (the harness appends one row per measurement, dated). license_tier: ORIGINAL. No hw writes (Rule 26).