Skip to content

Papers: model-merging implementation roadmap (34 papers triaged) - #1

Draft
shadyuwugurl wants to merge 1 commit into
mainfrom
papers/merge-methods-roadmap
Draft

shadyuwugurl wants to merge 1 commit into
mainfrom
papers/merge-methods-roadmap

Conversation

@shadyuwugurl

Copy link
Copy Markdown
Owner

Sketch PR tracking the paper backlog as implementable forge work.

What this PR contains (sketch):

  • TODO_PAPERS.md: 34 unique papers triaged into 20 merge ops (forge-merge, incl. forge-darwin/forge-train items), 2 eval-harness items (forge-eval BSM + PORTIA), E-PMQ pointer (already in README roadmap), MergeKit/survey references, 6 explicit out-of-scope with reasons.

Notable calls:

  • 2601.13572 agent-RAM collides with existing Ram - reserved name AgentRam / --method agent_ram.
  • 1811.11141 + 1912.09268 are one line (conference -> journal), single item.
  • KVMerger is inference-time (KV cache), not a MergeMethod.
  • Local artifact mirrors under hf://buckets/MC7ever/*-artifacts linked per item (DRM, MC-SMoE, KVMerger, TIME).

Acceptance per item (in doc): MergeMethod variant + mergekit parse/serialize + CLI dispatch (no silent linear fallback), smoke asserts + tiny round-trip, benchmax delta entry.

Follow-ups (not in this sketch): stacked implementation PRs per item, README R and D table sync, docs/mergekit_parity.md update.

Ready for review of triage/scope before implementation PRs start.

Sketch roadmap for paper backlog: 20 merge ops, 2 eval-harness
items, E-PMQ pointer, MergeKit/survey references, 6 explicit
out-of-scope with reasons. Per-item acceptance criteria.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant