Not a task — informational heads-up for the maintainers, nothing to implement. Close it freely.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
DeepDive earned a place on the map:
How we mapped it:
- built with
slime — DeepDive's multi-turn RL runs on THUDM's slime framework — the released training code is a slime rollout setup, and the repo credits it directly.
If you want it visible in your README, every mapped repo has a badge:
[](https://stackmap.shipwithai.xyz/repos/THUDM/deepdive?utm_source=badge)
It renders as StackMap | ↔ 2 typed links and links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
DeepDive earned a place on the map:
How we mapped it:
slime— DeepDive's multi-turn RL runs on THUDM's slime framework — the released training code is a slime rollout setup, and the repo credits it directly.If you want it visible in your README, every mapped repo has a badge:
It renders as
StackMap | ↔ 2 typed linksand links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.