📉 Sequential Forgetting Leaderboard

How much does sequential fine-tuning destroy what the model already learned? Lower magnitude = better retention. Every number links to the raw run file in the benchmark dataset; transcriptions are hand-checked (provenance). Suites are not cross-comparable; each table ranks within its own protocol.

Suite A — 5 real-world domains · Mistral-7B · 3 seeds

methodbase modeldomainsseedsmetricvalue %statussourcenotes
modular_crmaMistral-7B53holdout_NLL_drift-0.166valid_multiseedmultiseed_results_combined.jsonper-task LoRA + CRMA backbone; drift of saved snapshots re-run under final backbone
frozen_baseMistral-7B53holdout_NLL_drift1.948valid_multiseedmultiseed_results_combined.jsonno adaptation control
naive_sequential_loraMistral-7B53holdout_NLL_forgetting42.96valid_multiseedmultiseed_results_combined.jsonsingle LoRA trained sequentially across domains

Suite B — Medical→Legal→Code→Finance

methodbase modeldomainsseedsmetricvalue %statussourcenotes
modular_crmaMistral-7B-v0.341holdout_NLL_drift-0.1valid_single_runablation_v8.1_7b_results.mdavg of per-task drift table; NAIVE ref is the same run's forgetting avg
modular_crmaTinyLlama-1.1B-Chat-v1.041holdout_NLL_drift-0.1valid_single_runablation_v8.1_results.md
naive_sequential_loraTinyLlama-1.1B-Chat-v1.041holdout_NLL_forgetting225.3valid_single_runablation_v8.1_results.md
naive_sequential_loraMistral-7B-v0.341holdout_NLL_forgetting351.4valid_single_runablation_v8.1_7b_results.md

Suite B history — CL-technique stacks (within-version comparisons only)

methodbase modeldomainsseedsmetricvalue %statussourcenotes
cl_stack_v5_10componentTinyLlama-1.1B41holdout_NLL_forgetting58.4valid_single_runfull_ablation_history_v2_v8.md10-component stack; post-data-fix suite - NAIVE dropped 185.8->88.8 from data fixes alone
cl_stack_v3_ewc_gradprojTinyLlama-1.1B41holdout_NLL_forgetting91.3valid_single_runfull_ablation_history_v2_v8.mdEWC + gradient projection; pre-data-fix suite - compare only to its own NAIVE column
cl_stack_v7_replay_kd_freezeMistral-7B41holdout_NLL_forgetting109.3valid_single_runfull_ablation_history_v2_v8.mdreplay + knowledge distillation + bottom-layer freeze, Mistral-7B

Suite C — MQuAKE 5-skill retention · Qwen3-4B

methodbase modeldomainsseedsmetricvalue %statussourcenotes
modular_vault_slotsQwen3-4B-Instruct-250751accuracy_BWT0.0valid_single_runbwt_mquake_vault5_s42.jsonretention matrix R; BWT_k = R_final,k - R_k,k; mean over 4 earlier skills

Invalid & incomplete runs (disclosed)

Buggy or unfinished runs are relabeled, not deleted. Highlight: our early O-LoRA arm appeared to win (−2.0% forgetting) until we found a gradient-clipping bug that had frozen the model — so O-LoRA is listed as invalid, never validly measured here, not as beaten.

methodbase modeldomainsseedsmetricvalue %statussourcenotes
cl_stack_v2_olora_ewc_gradproj_replayTinyLlama-1.1B21holdout_NLL_forgetting-2.0invalid_disclosedfull_ablation_history_v2_v8.mdINVALID: PiSSA-init O-LoRA grad norms ~126678 vs clip 100 (ratio 0.00079) froze the model; the -2.0% 'win' is an artifact. O-LoRA has never been validly measured here
cl_stack_v4_cumulbasisTinyLlama-1.1B21holdout_NLL_forgetting27.8incomplete_disclosedfull_ablation_history_v2_v8.mdINCOMPLETE: run cut off mid-Phase-3; Phase-2-only numbers
cl_stack_v6_smaTinyLlama-1.1B21holdout_NLL_forgetting61.5incomplete_disclosedfull_ablation_history_v2_v8.mdINCOMPLETE: Sparse Memory Adapter crashed (OOM) at Phase 3; Phase-2-only numbers

Submit your method

  1. Run your method on a suite (protocol).
  2. Score it with scoring/score.py (--nll or --matrix).
  3. Open a PR on the dataset repo adding your raw log, a results.csv row, and a provenance line.

Single-seed submissions are accepted and labeled valid_single_run. If your run later turns out buggy, it moves to the disclosed section — that's the deal for everyone, including us.