kasohrab/theworld-spatial-channel-all warn
The chat template was dropped from its base model, which changes behavior; its architecture doesn't match its claimed base model.
claims base: google/gemma-3-4b-it · chat template: not found · view on Hugging Face ↗
Scan coverageStatic battery2026-08-21Weights batteryfailedBehavioral batterynot rundetails
| Battery | Looks at | Status |
|---|---|---|
| Static battery | Metadata & packaging | complete 2026-08-21 |
| Weights battery | Weights forensics — no GPU, no download | failedmax attempts exceeded |
| Behavioral battery | Live-inference differentials | not 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
google/gemma-3-4b-it 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 Architecture differs from claimed parent (the_world vs gemma3)
This model declares google/gemma-3-4b-it as its base, but its config declares architecture 'the_world' while the parent is 'gemma3'. A finetune, merge, or quantization cannot change the architecture family — the lineage label is wrong or misleading, so treat provenance claims (training data, safety posture, licensing) as unverified.
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.
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 kasohrab/theworld-spatial-channel-all
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 | the_world |
| parameters | 4443.9M |
| license | gemma |
| serialization | safetensors pickle |
| chat template | none |
| claimed lineage | google/gemma-3-4b-it |
| lineage verified | unverified — weights battery pending |
Full measured fingerprint
| architectures | Gemma3ForConditionalGeneration |
| library | transformers |
| pipeline | image-text-to-text |
| repo files | 15 — pickle: final/training_args.bin, training_args.bin |
| revision | 7f87b5993034 |
| HF snapshot | 410 downloads · 0 likes · updated 2025-11-18 · captured 2026-08-21 |
Verdict badge
Ship the verdict in your README — it always shows the latest published analysis:
[](https://ingot.tools/models/kasohrab/theworld-spatial-channel-all)