training · merge-capability-specialists-then-distil-student-prefixes TEC-0279 · proposed

Merge capability specialists, then distil on student prefixe

Train one RL specialist per execution capability from a shared backbone, merge their task vectors with TIES, then refine the merged student by distilling from the routed specialist teacher on the student's own generated prefixes.

Proposed. Filed by the drafting stage because a paper introduces or tests it. Nobody has vouched for it. The claim drafted from that paper is its first evidence, and what the paper used to validate it is in that claim’s source note. Say whether it held up for you, below.

Train one RL specialist per execution capability from a shared backbone, merge their task vectors with TIES, then refine the merged student by distilling from the routed specialist teacher on the student's own generated prefixes. Filed by the drafting stage from Capek 0.5: An Execution-Centric Vision-Language Model for Embodied Intelligence (2608.06756) with status proposed: the paper introduces or tests it, and the claim drafted from the paper is its first evidence. The paper validated it by: Controlled ablation on 35B-A3B against the shared backbone, four standalone experts, Mix-RL, TIES-only and MOPD-only across eight capability benchmarks; TIES+MOPD best on 3 of 8 and second on the other 5, improving 7 of 8 over MOPD alone. Also 28/34 and 30/34 matched benchmark rows improved over the Qwen initialisations, and EB-HAB success 46.0 to 63.0.. Nobody has vouched for it; add support or contest it on this page.

Addresses: Turning plans into physical action

Does it work?

nothing measured0 supporting · 0 contesting sources

Efficacy claims — what this technique actually moves, under which conditions, and whether that has been contested.

No efficacy claim filed yet. The technique is catalogued; whether it moves the capability, and when, is a separate assertion that needs its own sources.

No search recorded either, so this says nothing about the literature — only that nobody has looked here yet.

Code

No repository linked yet. Contribute one.

Sources

Either way, bring evidence: a link, or what you saw.

Whether a technique works is a claim. What you file here becomes a claim about this technique under the capability it addresses, with your evidence as its source, and moves the standing above the same way a paper would.