pblrvo/Qwen3-8B-Game-semantic-IDs-v3 warn
claims base: Qwen/Qwen3-8B · chat template: present · view on Hugging Face ↗
Scan coverage
Ingot runs three batteries against a model. What each one checks →
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics — no GPU, no download | complete 2026-08-21152,695-token embedding scanned · 2999 undertrained · lineage consistent |
| Behavioral battery | Live-inference differentials | not run |
Findings
Scanned 2026-08-21 · published from a community scan.
medium Chat template dropped vs parent
Qwen/Qwen3-8B ships a chat template; this repo does not. Serving stacks will silently fall back to a generic template, changing behavior. (In our 296-model census, 78% of pure quantization re-releases changed or dropped the template.)
How to fixingot patch
Restore the parent's chat template in `tokenizer_config.json` — a pure metadata fix.
- Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
- Or fix by hand: copy the `chat_template` value from the parent repo's `tokenizer_config.json` into this model's, and pin your serving stack to that file.
- If the drift was intentional (the author retrained on a new template), confirm that in the model card before "fixing" it — restoring the parent template on retrained weights changes behavior too.
medium Vocabulary size differs from claimed parent (152695 vs 151936)
A changed vocab means changed tokenization: strings will split differently than on Qwen/Qwen3-8B, which can shift behavior on identifiers, codes, and non-English text.
How to fixweight-level
Not patchable: the vocab size mirrors the embedding matrix in the weights. Verify the change was intentional.
- Do not edit `vocab_size` in config.json to "match the parent" — it must equal the embedding table in the shipped weights or the model won't load.
- Diff the tokenizers (`tokenizer.json` / added_tokens) against the parent to see what was added or removed, and test your own identifiers, codes, and non-English text through both.
- If the drift is unexplained by the model card, treat tokenization-sensitive behavior as unvalidated on this model.
medium Undertrained (glitch) token surface in vocabulary
Embedding-norm scan flagged 2999 undertrained tokens (norm < 0.3× the vocabulary median of 1.451), including 102 plain-ASCII strings that can appear in ordinary input as identifiers — e.g. "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte". In models where this class was tested behaviorally, such tokens silently rewrote user input into confident, schema-valid, wrong output. These are candidates from the weights alone; behavioral confirmation requires the behavioral battery.
How to fixruntime guardweight-level
Keep the affected token strings out of the model's input — the scan-derived runtime guard carries this model's exact blocklist.
- Fetch this model's guard artifact (`/api/v1/guard/<owner>/<model>`): the confirmed corrupting tokens and the low-norm candidate list, derived from the published scan.
- Screen inbound text with it (the `@ingotai/guard` package is a reference implementation) and route flagged records to a different model or human review — verbatim-copy tasks on flagged strings are the failure mode.
- The underlying cause is undertrained embeddings in the weights; a true fix is weight-level (continued pretraining on the affected tokens) — that is not a patch, it's a training job.
info Weights consistent with claimed parent Qwen/Qwen3-8B
Mean cosine similarity of 64 sampled token-embedding rows against Qwen/Qwen3-8B is 1.000 — the weights plausibly descend from the declared base (relation: unspecified).
How to fix
Fix or verify the `base_model` declaration so lineage checks can run.
- If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
- If you don't: identify the true parent (config architecture + weight shapes narrow it fast) and re-scan with that lineage in mind.
Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.
Fingerprint
The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-21.
| architecture | qwen3 · 36 layers · 4096-dim |
| parameters | 8197.0M |
| vocabulary | 152,695 tokens |
| license | apache-2.0 |
| serialization | safetensors |
| chat template | none |
| claimed lineage | Qwen/Qwen3-8B |
| lineage verified | consistent vs Qwen/Qwen3-8B — embedding-row cosine 1.000 |
| glitch-token surface | 2,999 undertrained candidates, 102 plain-ASCII |
Full measured fingerprint
| architectures | Qwen3ForCausalLM |
| library | transformers |
| pipeline | text-generation |
| repo files | 9 |
| revision | 1aa71a0190e8 |
| HF snapshot | 1.1k downloads · 0 likes · updated 2026-08-14 · captured 2026-08-21 |
| embedding tensor | model.embed_tokens.weight · BF16 · 152,695×4096 |
| embedding norms | median 1.4513 · mean 1.3778 |
| lineage check | consistent — cosine 1 over 64 sampled rows vs Qwen/Qwen3-8B |
| glitch-token samples | "$PostalCodesNL", "ForCanBeConvertedToF", "PostalCodesNL", "ForCanBeConverted", "useRalative", "thuisontvangst", "useRal", "sexkontakte", "NdrFc", "webElementX", "sextreffen", "wannonce" |
Battery runs
The run trace behind the findings above: every deep-battery job for this model, with what each run measured or why it failed. Findings are only as good as the runs that produced them.
| battery | status | queued | duration | attempts |
|---|---|---|---|---|
| weights | complete | 2026-08-21 05:12 | 4m | 1 |
weights run 2026-08-21 — measurements
| probes run | glitch-norm-scan, lineage-norm-correlation |
| embedding tensor | model.embed_tokens.weight · BF16 · 152,695×4096 |
| glitch surface | 2,999 undertrained, 102 plain-ASCII |
| lineage check | consistent — cosine 1 over 64 rows vs Qwen/Qwen3-8B |
Fix it
Some findings are metadata-level and patchable — apply the fixes to your local copy (your weights never leave your machine):
npx @ingotai/scan patch pblrvo/Qwen3-8B-Game-semantic-IDs-v3
Remediation guidance addresses the documented findings only. It is evidence-driven repair, not a safety certification of the model.
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/pblrvo/Qwen3-8B-Game-semantic-IDs-v3)