Researchers from Universidad Politécnica de Madrid and Purdue University published Decoding-Level Taboo, a diagnostic tool that measures how LLMs perform in real production deployments rather than benchmark conditions. Production systems don't send clean prompts. They layer system instructions, safety guardrails, and structured output rules that push generation off the model's training path.
Taboo's mechanism is direct. Rather than crafting adversarial prompts, the test intervenes in logit space at runtime. At each word boundary, Taboo masks the model's top candidate tokens, forcing circumlocution—expressing the same semantic intent through secondary vocabulary. The result is a clean signal on off-path generation quality without external verifiers, labeled data, or fine-tuned judges. The only cost is inference.
Across open-weight model families, the authors find two dominant drivers of off-path robustness: parameter scale and post-training instruction alignment. Larger models perform better. Better-aligned models also perform better, largely independent of size. The paper does not publish a composite leaderboard score, so teams cannot directly compare checkpoints on a Taboo index. The community needs public Taboo runs on named checkpoints before it feeds into model selection pipelines.
The benchmark-deployment gap Taboo targets is widely documented. Public MMLU rankings do not predict workload performance because enterprise inputs—long system prompts, RAG context, structured output schemas, multi-turn history—differ radically from standardized benchmarks. Providers update model behavior under stable version numbers without always communicating changes. A model that passed internal evaluation three months ago may handle system-prompt composition differently today. Taboo gives teams a repeatable runtime probe that doesn't depend on fixed eval datasets, making it more robust to contamination than static benchmarks.
The secondary applications are potentially as valuable as the primary diagnostic. By forcing circumlocution, Taboo generates natural diversity in synthetic training data—useful for fine-tuning datasets that need lexical variety without semantic drift. It also stress-tests safety guardrails directly. If a model under constraint routes around a guardrail's trigger vocabulary, that's a signal worth catching before deployment. Kalvium Labs measured guardrail bypass rates across four client projects: regex-based input filters caught 60–70% of injection attempts, while LLM-based classifiers reached 89–94%. Neither accounts for model behavior changes induced by structural output constraints—which Taboo probes.
| Guardrail Type | Injection Attempt Detection Rate | Gap Taboo Addresses |
|---|---|---|
| Regex-based input filters | 60–70% | Does not account for behavior changes under structural output constraints |
| LLM-based classifiers | 89–94% | Does not account for behavior changes under structural output constraints |
Taboo requires no access to model weights. The logit-space intervention works against any model that exposes logit outputs or token probabilities, covering every major open-weight serving stack (vLLM, TGI, Ollama) and any provider that surfaces log-probs via API. Teams running their own inference on Llama, Mistral, or Qwen families can drop Taboo into a pre-deployment checklist without modifying architecture or retraining.
| Category | Name | Required API Feature |
|---|---|---|
| Open-weight serving stack | vLLM | Logit outputs / token probabilities |
| Open-weight serving stack | TGI (Text Generation Inference) | Logit outputs / token probabilities |
| Open-weight serving stack | Ollama | Logit outputs / token probabilities |
| Model family (self-hosted) | Llama | Logit outputs / token probabilities |
| Model family (self-hosted) | Mistral | Logit outputs / token probabilities |
| Model family (self-hosted) | Qwen | Logit outputs / token probabilities |
| Commercial API provider | Any provider exposing log-probs | Log-probs endpoint |
Taboo is the first cheap, verifier-free tool for measuring how gracefully a model degrades when structural constraints narrow its generation corridor. Run it before committing a checkpoint to production, and again after any provider update.