Model page

thoughtworks/cbd-gemma2-9b-100pair-refusal-v1 warn

downloads 247likes 0license gemmaarch gemma2params 9241.7Mupdated 2026-07-19

claims base: google/gemma-2-9b-it · chat template: present · view on Hugging Face ↗

Scan coverage

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

BatteryLooks atStatus
Static batteryMetadata & packagingcomplete 2026-08-21
Weights batteryWeights forensics — no GPU, no downloadcomplete 2026-08-21256,000-token embedding scanned · 0 undertrained · lineage consistent
Behavioral batteryLive-inference differentialsnot run

Findings

Scanned 2026-08-21 · published from a community scan.

medium Chat template dropped vs parent

google/gemma-2-9b-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.

  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.

info Embedding-norm glitch scan clean

No undertrained tokens found: every non-special token's embedding norm is above 0.3× the vocabulary median (1.701). The glitch-token data-corruption class has no candidate surface in this model.

info Weights consistent with claimed parent google/gemma-2-9b-it

Mean cosine similarity of 64 sampled token-embedding rows against google/gemma-2-9b-it 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.

  1. If you own the repo: correct the `base_model` field in the model card metadata to the real, public parent.
  2. 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.

architecturegemma2 · 42 layers · 3584-dim
parameters9241.7M
vocabulary256,000 tokens
licensegemma
serializationsafetensors pickle
chat templatenone
claimed lineagegoogle/gemma-2-9b-it
lineage verifiedconsistent vs google/gemma-2-9b-it — embedding-row cosine 1.000
glitch-token surfaceclean no undertrained tokens
Full measured fingerprint
architecturesGemma2ForCausalLM
librarytransformers
pipelinetext-generation
repo files19 — pickle: training_args.bin
revisione08317fccdf3
HF snapshot247 downloads · 0 likes · updated 2026-07-19 · captured 2026-08-21
embedding tensormodel.embed_tokens.weight · BF16 · 256,000×3584
embedding normsmedian 1.7011 · mean 1.7216
lineage checkconsistent — cosine 0.9999 over 64 sampled rows vs google/gemma-2-9b-it

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.

batterystatusqueueddurationattempts
weightscomplete2026-08-21 05:162m1
weights run 2026-08-21 measurements
probes runglitch-norm-scan, lineage-norm-correlation
embedding tensormodel.embed_tokens.weight · BF16 · 256,000×3584
glitch surface0 undertrained, 0 plain-ASCII
lineage checkconsistent — cosine 0.9999 over 64 rows vs google/gemma-2-9b-it

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 thoughtworks/cbd-gemma2-9b-100pair-refusal-v1

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:

Ingot verdict: warn

[![Ingot scan](https://ingot.tools/api/v1/models/thoughtworks/cbd-gemma2-9b-100pair-refusal-v1/badge.svg)](https://ingot.tools/models/thoughtworks/cbd-gemma2-9b-100pair-refusal-v1)
Gate it in CI