A live compatibility graph for ML training components. Pick your optimizer, scheduler, quantization, technique. Incompatible tools grey out instantly with cited evidence from real practitioner runs. Greyed means not yet satisfied, not forbidden — add the missing ingredient and watch it re-light.
Pick optimizers, schedulers, quantization, techniques. The graph re-resolves live and tells you what fits, what's missing, and what blows up — every fact backed by a citation.
Pick a component and every other one re-styles by status: available, conditional, or blocked. Greyed means not yet satisfied — add the missing ingredient and it re-lights in real time.
Every grey-out, every fix, every conflict carries its cited source — verbatim quote, URL, and tier badge. Hover anything to see where the claim comes from.
Scheduler picks aren't picked from a paper — they're picked from real measured val_loss / val_acc on distilbert / sst2, three seeds each. DLRS leads. OneCycle is flagged above cohort cutoff.
Sixty seconds, three motions. The demo path the team built it around.
The left rail is your loadout. Tap any optimizer, scheduler, technique,
quantization, architecture, or inference engine. The instant you equip one,
the graph re-runs POST /resolve and re-styles every other node by status.
The right rail is your crafting window. Conflicts are scored in rust. Unmet requirements glow amber with a one-tap + add bnb 4-bit button. Benchmark-backed scheduler picks list themselves by measured val_loss with the leader marked with a star.
Hover any node, edge, or recipe entry to surface the verbatim quote from its source and the tier badge it earned. T1 is Rick's own verified runs (immutable). T2 is community-corroborated. T3 is single-source — lives in the review queue until something else agrees.
optimizer_grouped_parameters — adamw_8bit's default decay/no-decay split silently no-ops per-layer LR.We don't assert nonsense as fact. Three tiers, three colors, three weights. The scraper feeds the bottom; corroboration promotes upward.
Rick's own research notes and reproduced runs. Immutable — the scraper can never overwrite these, only add corroboration.
Official docs, or two-plus independent sources agree. The bulk of the workable graph.
One scraped report, no corroboration yet. Lives in the review queue. Promotes when something else agrees, or when Rick signs off.
A Bright Data scraper hunts SERP results in English and Chinese, extracts (A, relation, B, conditions, fix, quote) tuples with Haiku, resolves them against canonical node aliases, and proposes them to the review queue.
Watch the Live Discoveries hearth at the bottom of the Forge while you work — new edges literally rise out of it as the scraper corroborates them. The graph is alive.
English-only sources miss large chunks of the Chinese ML ecosystem. We cover both. The scraper writes nothing to T1 — that's Rick's territory. Single-source claims sit at T3 in the queue and only ascend with evidence.
Ninety seconds. Ten components. One recipe that actually compiles.
Enter the Forge