BD × AI LAB · TSP R&D
Current research architecture · evidence cut 18 September 2026

Six arenas.
Six different questions.

The TSP program is no longer one solver with several parameter sets. It is a portfolio of six deliberately different research lines. Some optimize public benchmark quality, some attack the hard tail, some falsify representation hypotheses, and the two 8zTSP-R branches explore native relational and description-complexity search without pretending to be the same product.

6distinct research lines
5 / 9TSPES instances exact
11,355TSPES lu980 vs 11,340 optimum
96,780nu3496 DEV2.3 / DEV2.4

Why six?

Because one leaderboard would flatten different scientific roles. A strong product solver, a plateau donor, a hard-tail successor, a falsification arena and two native research systems should not be judged by one scalar.

Solver strength

TSPES asks whether the mature family can solve standard instances extremely well.

Causal hard-tail comparison

DEV2.3 and DEV2.4 ask whether architectural changes actually beat the proven donor.

Representation discovery

RPHS and both 8zTSP-R branches test mechanisms that may matter only at particular scales, phases or representations.

The six lines

Current numbers below use the verified 18 September Home extract, with retained Work evidence where that branch is Work-hosted. Historical numbers are explicitly marked as such.

1 · TSPES v0.1.4.2 W6 RUNNING · FLAGSHIP

Mature product / solver research

The strongest current solver line. Exact optimum has been reached on wi29, dj38, qa194, uy734 and zi929. Fresh 22 September evidence has active lu980 = 11,352 versus optimum 11,340: only 12 units remain, a 0.105820% gap. The active continuation is at cycle 2 with 563,748 committed proposals.

5 / 9 exacttracked benchmark ladder
0.105820%current lu980 gap
W6workers
563,748active-cycle proposals
2 · DEV2.3 RUNNING · PLATEAU

Proven nu3496 hard-tail donor

The continuous donor remains at 96,780 on nu3496, 648 above the 96,132 optimum. Direct 22 September Cockpit status shows the native process ALIVE at cycle 26 / branch index 3 / 178 variants completed. The 96,780 campaign incumbent predates the current native branch, so it is not attributed to that branch.

96,780campaign incumbent
0.674073%gap
branch 3native status index
178variants completed
3 · DEV2.4 HF3 RUNNING · TIED

Hard-tail successor / control

DEV2.4 has physically exercised the strict hybrid GPU+Rust stack and still holds 96,780 after 893,426 global proposals. The fresh committed checkpoint is generation 55,935 in the direct native status. Independent validation remains PASS. Added search has not improved the incumbent, which is useful negative evidence rather than superiority.

96,780best length
893,426global proposals
PASSindependent validation
gen 55,935native checkpoint
4 · BD-RPHS v0.1.2 W4 RUNNING · SATURATED

Representation / sensor falsification line

Active uy734 W4 remains at 79,288 / 79,114 = 0.219936% and has advanced to cycle 226 / 1,811 completed chunks. The same numerical best previously appeared in historical W6 under the N2_shuffled_reverse null control; active W4 carries A1_scale_coherence. The matched numerical result is real while causal interpretation remains open.

79,288active W4 best
cycle 2261,811 completed chunks
A1 scale coherenceactive W4 best arm
null controlhistorical W6 winner
5 · 8zTSP-R v0.1.1 R2/HF1 RUNNING · RESEARCH

Pure relational / native discovery

This line is not a competitive product solver. All 9 of 9 instances have committed snapshots. Fresh Work evidence has advanced the campaign to round 241; the latest verified completed visit is rw1621, while the current pending instance is mu1979 with 15,408 proposals committed toward a 15,424 target. Representation value remains contextual rather than universal.

9 / 9committed instance snapshots
round 241campaign checkpoint
mu1979current pending instance
Rank, Don't Eliminatesupported research lesson
6 · 8zTSP-R v0.2.0 HF2 MVC RUNNING · EARLY

Multi-View Compression Native

The newest line asks the founding compression question most directly: can multiple description-complexity views become useful search coordinates? It has eight matched lanes including legacy compression, CMVC, combined views, compression-blind and native-distance controls. The fresh committed snapshot is at generation 8 with 32/64 proposals and best length 43,487. No full visit has completed yet, so no performance-advantage claim is made.

8 lanesmatched compression/control design
wi29startup instance
gpu-strictrequested backend
gen 8 · 32/64committed proposals
What is strongest today? TSPES is the strongest demonstrated solver line. DEV2.3/DEV2.4 carry the strongest nu3496 hard-tail evidence. The old 8zTSP-R line carries the strongest current methodological signal about late/contextual value. The new MVC line carries the highest uncertainty—and therefore the highest near-term information value.
Research → product transfer: TripOpti. The six arenas remain six. TripOpti is the browser deployment branch that distills selected TSP mechanisms into Fast, Deep and experimental Deep · MDL×DCC modes; it is not a seventh research arena.
Claim discipline. A shared 96,780 incumbent does not make DEV2.4 an independent algorithmic replication of DEV2.3. RPHS's historical 79,288 must be shown with its null-control winner. The old 8zTSP-R line must not be marketed as competitive TSP solving. MVC now has fresh committed run behavior, but remains unranked until completed visits support a fair comparison.