Views
No views yet
Qwen/Qwen3.6-27B (not any descendant), as their base model — so all task vectors $\Delta$ live in the same reference frame, which is what makes the superposition meaningful. Stage 3. re-anchors the entire result of the first two stages:cold_amp below).⚠️ In this release the retention coefficient $W_{V3} = 0.30$ (not 1.00), so the output is $\text{Qwen3.6} + 0.30 \cdot T(\Delta_{v3}) + 1.00 \cdot \Delta_{\text{ColdFusion}}$. Since $\beta = 1.00$, the base has already landed entirely on Cold-Fusion (Qwen3.8); $\alpha$ only controls how much of the Qwen3.6-side task vector is added. The choice $\alpha = 0.30$ was measured and calibrated, not picked arbitrarily: before construction we measured that Cold-Fusion's displacement relative to official Qwen3.8 is only $\approx 0.7,|W|$ (i.e., in Cold-Fusion − Qwen3.6, 98.7% is generation difference and only 1.3% is its own fine-tuning), while $\Delta_{v3}$ is about $13,|W|$ on the MLPs and nearly orthogonal to it (measured cosine $= +0.005$). With $\alpha = 1.00$, Cold-Fusion's behavior would be drowned out at roughly 15× the volume; with $\alpha = 0.30$, the displacement landing on the MLPs is ≈ 4.6× that of $\delta_{CF}$ (before $T$ truncation).
lora_alpha = α×48; this repo ≡ Cold-Fusion + 0.30·that direction), so it can be applied to any Qwen3.8-family model. embed_tokens / lm_head were not passed through $T$ due to memory limits and are not included in the adapter.1# ===== stage 1: build the "general intelligence composite" G =====
2merge_method: della_linear
3base_model: Qwen/Qwen3.6-27B
4models:
5 - model: DavidAU/Qwen3.6-27B-V1.1-FF711-Darker-Hero-GAIN-H2.0
6 parameters: { weight: 0.90, density: 0.85 }
7 - model: YFC-112358/Qwen3.6-27B-Della-Deckard-Isometry-Geodesic-v2
8 parameters: { weight: 0.80, density: 0.85 }
9 - model: nightmedia/Qwen3.6-27B-Seven
10 parameters: { weight: 0.25, density: 0.55 }
11parameters:
12 epsilon: 0.30
13 lambda: 1.0
14 normalize: false
15 int8_mask: true
16dtype: float32
17out_dtype: bfloat16
18tokenizer: { source: "Qwen/Qwen3.6-27B" }
19
20# ===== stage 2: G vs #4, with #4 dominant =====
21merge_method: task_arithmetic
22base_model: Qwen/Qwen3.6-27B
23models:
24 - model: KyleHessling1/Qwopus3.6-27B-Fusion-BF16
25 parameters: { weight: 1.00, density: 1.00 }
26 - model: ./stage1-G
27 parameters:
28 weight: [1.0, 1.0, 1.0, 1.0]
29 density: 1.00
30parameters:
31 epsilon: 0.30
32 lambda: 1.0
33 normalize: false
34 int8_mask: true
35dtype: float32
36out_dtype: bfloat16
37tokenizer: { source: "Qwen/Qwen3.6-27B" }
38
39# ===== stage 3: re-anchor the whole stage-2 output onto Cold-Fusion (3.8) =====
40merge_method: task_arithmetic
41base_model: Qwen/Qwen3.6-27B
42models:
43 - model: DavidAU/Qwen3.8-27B-Cold-Fusion-GAIN-V1.1
44 parameters: { weight: 1.00 }
45 - model: ./stage2-out
46 parameters: { weight: 1.00 }
47parameters:
48 normalize: false
49 int8_mask: true
50dtype: float32
51out_dtype: bfloat16
52tokenizer: { source: "DavidAU/Qwen3.8-27B-Cold-Fusion-GAIN-V1.1" }Qwen/Qwen3.6-27B as their reference frame and both have weight 1.00, so $\text{base} + (\text{CF} - \text{base}) + (\text{stage2} - \text{base}) = \text{CF} + \text{stage2} - \text{base}$.⚠️ This step is a cross-generation linear transport with no mathematical guarantee. The Qwen3.6 and Qwen3.8 architectures are identical field by field (hidden 5120 / 64 layers / vocab 248320 / FFN 17408 / MTP included / vision tower included), so all shape checks pass green and the model loads — but that does not prove the two generations' weights live in the same base. The measuredcold_ampis given in the table below: continued training on the same base should land in 0.02–0.20; if it were close to 1.0, that would mean two independent pre-trainings, and this step would be adding noise.
density values exactly (fable and v2 both have density 0.85 ⇒ ε was narrowed to 0.13 for both). In stage 2 both sources have density 1.00 with no pruning, so ε automatically goes to zero — that part has no randomness at all.| Metric | Meaning | Median value |
|---|---|---|
| amp | $|\text{total increment}| / |\text{ancestor weights}|$ | 0.0202 |
| share | Mass ratio of G to Qwopus | 26.002 |
| kill₂ | Fraction of non-zeros eliminated by stage-2 sign election | 0.0% |
| cold_amp | $|\text{Qwen3.8·ColdFusion} - \text{Qwen3.6}| / |\text{Qwen3.6}|$ | 0.1217 |
1from transformers import AutoModelForCausalLM, AutoTokenizer
2m = AutoModelForCausalLM.from_pretrained("YFC-112358/Qwen3.8-27B-Della-Deckard-Fable-Qwopus-ColdFusion-v4", dtype="bfloat16", device_map="auto")
3t = AutoTokenizer.from_pretrained("YFC-112358/Qwen3.8-27B-Della-Deckard-Fable-Qwopus-ColdFusion-v4")temperature=0.7, top_p=0.8, top_k=20. The config/tokenizer comes from the Cold-Fusion (3.8) repo — the weights are anchored on that side.task_arithmetic. The reason for doing it this way: per-source audits showed Qwopus's increment relative to its ancestor is concentrated in the MLPs and only 0.2–0.8% in magnitude — pruning another 40% off such a small increment would cut signal and leave noise.cold_amp at construction time: 0.1217; the reference range for same-base fine-tuning is 0.02–0.20. If that value were close to 1.0, treat this model as an experiment. Also, Cold-Fusion-GAIN-V1.1 was still at the author-annotated "cook #1 / working title" stage when constructed, and its weights may have since been replaced; specify a commit if you want an exact reproduction.della_linear). The task vectors of v2 and Fable are nearly orthogonal (cos ≈ 0.01); with election on, Fable would be the majority direction and about half of v2's retained elements would be wiped out (measured kill ≈ 13%, exactly the order of half of v2) — effectively projecting away v2's orthogonal features. To preserve it fully, election was disabled this time.