← TinyGPT · docs · devlog · roadmap · speedup
source: docs/prds/GPU-RESEARCH-BACKLOG.md · view on GitHub ↗

GPU / research backlog — what’s left, and how to do it

The PRDs below can’t be finished-and-verified in a CPU sandbox: they need a GPU (training is the deliverable), special hardware, network installs, or are multi-week from-scratch model builds. The verifiable scaffolding ships (eval gates, tinygpt generate, recipes) — what remains is the run/implementation. This is the implementation outline for whoever picks them up on a GPU box.

Honesty note: I deliberately did not write thousands of lines of untested model internals (a from-scratch VLM/diffusion/TTS in one shot would be a hallucinated approximation). Each entry is an outline, not fake code.

Specialist training tier (eval gate + generate already ship)

The pipeline is built: sft --llrdtinygpt generate → the eval gate. What’s left is the GPU run + (for some) a domain parse step.

Quantized-training tier

Inference / port tier

Hardware / network runs (no new code)

Tier 5 — multi-week from-scratch model builds

Each is a research project, not a session task. Outlines:

See docs/prds/STATUS.md for the per-PRD verdicts this complements.