onefrontieronefrontier.ai

Qwen/Qwen2.5-7B-Instruct

apache-2.0 no launch

text-generation · 7.62B parameters · 14.2 GiB of weights at revision a09a3545. Runs on a single GPU when the source verified it.

Did this card launch? The count is real — it comes from launches the kit recorded against this path, not from a widget anywhere.

1checkpoints
0published launches
1GPU minimum
3named gaps
The identity, read from the HF API at the revision the card pins.
weight pathQwen/Qwen2.5-7B-Instruct
revisiona09a35458c702b33eeacc393d103063234e8bc28
licenseapache-2.0
gatedno
parameters7.62B
weight bytes14.2 GiB
modalitytext-generation
HF downloads5.4M at capture
last modified2025-01-12T02:10:10.000Z

The checkpoints.

Every servable variant in or beside the repo. resident_gib is what lands in VRAM after load; host_gib is what stays on the host and never touches the card.

name format location resident host tier gated
root bf16 repo root 14.2 GiB — no

root — 4 weight file(s)

No published launch.

Neither vLLM nor SGLang publishes a launch for this path at capture. The card says so rather than composing a command that has never run: that is what the gap list below is for.

Every floor a box must clear.

A launch that fails on the third requirement wasted the first two. These are the requirements, as data — the fit gate reads them instead of a paragraph.

The hardware block, verbatim from the card.
GPU modelsnone validated
architectures—
min GPUs1
TP ruleno published TP; single-GPU or unstated
min VRAM / GPU—
min total VRAM—
min disk67 GiB
min host RAM—
interconnectnot required
CUDA min—
driver min—
context tokens—

The 3 things this card could not answer.

First-class, not swallowed. Every entry is a field a source did not answer — which makes it a launch nobody has done, and therefore a unit of work rather than a defect.

envs.vllm no published vLLM recipe for this repo
envs.sglang no SGLang cookbook page matched this repo
hardware.validated no source marks a hardware family verified

The file.

The card is a YAML document with a published JSON Schema. View it, download it, diff it against the next capture — and point one at it.

download

Same bytes the collector wrote. The JSON is the same card, for a machine that would rather not parse YAML.

with one

one launch --card Qwen/Qwen2.5-7B-Instruct/launch-card.yaml

one follows the argv above, checks the floors before the paid clock, and on a failure changes exactly one field and retries — recording every attempt against this path.

Where every field came from.

The card is assembled, not authored. These are the sources, so a reader can check the claim rather than trust it.

Captured 2026-10-31T17:28:35Z by hf-api + vllm-recipes + sglang-cookbook. Schema onefrontier.launch-card/v1.