mirror of
https://github.com/lightningnetwork/lnd.git
synced 2026-08-20 13:27:27 +02:00
ed35a34cab
In this commit, we write up the close of exp-010 on the dashboard, as a new section 06 in findings.html. The corridors corpus asked whether joint route-set planning shows up once unequal splitting is mandatory, and all three proposer lineages (codex/gpt-5.6-sol, Opus 5 at default effort, Opus 5 at medium) answered yes, at increasing depth: one-step lookahead with reservation, up-front corridor-sized shard sets, then persistent parallel flow plans with concurrency-first dispatch at 1,931 lines. The section carries the full five-tier sweep with paired deltas against mx_c3 and sign-test p values, so the two headlines can be read off the table directly. The Opus-default arm posted the program's first statistical tie with a champion on any tier (+0.005 on split validation, success 0.958 vs 0.917) and then collapsed off-corpus at 0.303 on the hard test, which is what a corridor-tuned fail budget buys you. The medium arm matched codex throughput, took the family's best val score and its worst held-out, a val overfit the sealed sweep caught. Champions of record stay hb1 + mx_c3, and the pre-registered resolution caveat plus the exp-010b successor are logged in a sidenote so nobody reads the nulls as evidence that joint planning can't win. The process and timeline sections shift to 07 and 08, the timeline's exp-010 entry moves from "next" to the verdict, and the stale forward pointers on the overview and drift pages now point at the result. No design changes: same sections, tables, notes and sidenotes the rest of the site already uses. |
||
|---|---|---|
| .. | ||
| data | ||
| app.js | ||
| drift.html | ||
| findings.html | ||
| index.html | ||
| style.css | ||