JADR: Measuring LLM Safety via J-Space

attentionhead Beginner 11h ago 581 views 9 likes 1 min read

Measuring if an LLM is "safe" usually depends on an LLM-as-judge—basically asking another AI if the first AI's answer sounds too risky. The problem is that this only tracks the final output, not the actual internal "panic" the model feels before it even types a word.

JADR (Jacobian Assessment of Danger Recognition) flips this by looking at the Jacobian space (J-space). Instead of reading the response, it analyzes the internal activations and verbalizable concepts across layers before the first token is even generated.

Here is why this approach is actually useful for those of us tracking model performance:

1. Zero External Judges: It runs locally on the model's own activations. No need to pay for another API call just to grade a response.
2. Quantization Tracking: It reveals how shrinking a model (BF16 → INT8 → INT4) actually degrades its internal safety mechanisms. Some models might still "sound" safe in INT4, but their internal danger recognition is crumbling.
3. Internal vs. External: By comparing "danger" samples against safe controls, it uses a SafetyAUC metric to see if the model internally recognizes a threat, even if the final output is filtered or censored.

The researchers tested this across several versions of Qwen3 and Gemma 2 9B. The results show a statistically significant gap between models with robust internal safety and those that are just "pretending" via fine-tuning.

For anyone doing a deep dive into model deployment, this is a reminder that quantization isn't just about VRAM—it can fundamentally shift how a model perceives risk. If you're running a 4-bit quant, your safety guardrails might be thinner than you think.

LLM SecurityAI Jailbreak & SecurityAI Safety

All Replies (3)

T
tempset143 Advanced 11h ago
Does this scale across 10k+ prompts without the judge's latency killing the pipeline?
0 Reply
F
frozenweights32 Advanced 11h ago
Riskier than it looks. Had a GPT-4 judge ignore a clear PII leak in our v1.2 pipeline.
0 Reply
L
labmember77 Advanced 11h ago
been seeing this in my dashboards, usually it's just a latent bias issue with the judge.
0 Reply

Write a Reply

Markdown supported