Model page

pblrvo/Qwen3-8B-Game-semantic-IDs-v3 warn

The chat template was dropped from its base model, which changes behavior; its tokenizer differs from its claimed base model; glitch tokens that can silently corrupt ordinary input.

downloads 125likes 1license apache-2.0arch qwen3params 8197.0Mupdated 2026-08-14

claims base: Qwen/Qwen3-8B · chat template: present · view on Hugging Face ↗

Scan coverageStatic battery2026-08-21Weights battery2026-08-21Behavioral batterynot rundetails
BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics: no GPU, no downloadcomplete 2026-08-21152,695-token embedding scanned · 2999 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Ingot runs three batteries against a model. What each one checks →

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.

  1. Run `ingot patch <owner/model>` — the patch manifest carries the parent's template and applies it to a local copy's `tokenizer_config.json`.
  2. 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.
  3. 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.

  1. 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.
  2. 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.
  3. 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.

  1. 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.
  2. 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.
  3. 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).

Put this result in your workflow

Check every checkpoint before it ships

Use the web app, API, CLI, or CI gate to scan candidate checkpoints and catch model drift before deployment. Public-model scans publish to the open database; paid plans add the volume needed for continuous checks.

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.

Fingerprint

The durable profile of this model: measured weights-and-metadata facts, rebuilt on every scan and battery run. Updated 2026-08-21.

architectureqwen3 · 36 layers · 4096-dim
parameters8197.0M
vocabulary152,695 tokens
licenseapache-2.0
serializationsafetensors
chat templatenone
claimed lineageQwen/Qwen3-8B
lineage verifiedconsistent vs Qwen/Qwen3-8B — embedding-row cosine 1.000
glitch-token surface2,999 undertrained candidates, 102 plain-ASCII
Full measured fingerprint
architecturesQwen3ForCausalLM
librarytransformers
pipelinetext-generation
repo files9
revision1aa71a0190e8
HF snapshot1.1k downloads · 0 likes · updated 2026-08-14 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 152,695×4096
embedding normsmedian 1.4513 · mean 1.3778
lineage checkconsistent — 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 (1)the run trace behind the findings — what each job measured
batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:124m1
weights run 2026-08-21 — measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 152,695×4096
glitch surface2,999 undertrained, 102 plain-ASCII
lineage checkconsistent — cosine 1 over 64 rows vs Qwen/Qwen3-8B

Verdict badge

Ship the verdict in your README — it always shows the latest published analysis:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/pblrvo/Qwen3-8B-Game-semantic-IDs-v3/badge.svg)](https://ingot.tools/models/pblrvo/Qwen3-8B-Game-semantic-IDs-v3)
Gate it in CI