Shieldstral : Mistral compile sa doctrine en 3,8 milliards de paramètres
A watch note by **Didier Girard** published on **X** on **August 7, 2026**, which reads the launch of **Shieldstral 1.0 3B** (Mistral AI, August 4, 2026) not as a product release but as **the production deployment of a doctrine**. Starting point: on **May 13, 2026**, before the National Assembly's commission of inquiry into digital vulnerabilities, **Arthur Mensch** refused any oversight role for Mistral over the end use of its models — *"we do not have democratic legitimacy"* — explicitly rejecting **Anthropic**'s stance. Less than three months later, Mistral releases a **moderation model**. The author dismisses the apparent contradiction: **Shieldstral carries no taxonomy of the licit and the illicit**, it answers a **question the user writes**. **The mechanism is the heart of the note**: a three-part prompt (context + severity / a single closed question / the content to be judged), a `yes` or `no` response, and the **softmax over these two tokens** produces a continuous score between 0 and 1. **The moderation policy is not in the weights, it is read at inference time** — whereas **Llama Guard 4** embeds the MLCommons taxonomy fixed at training time, Shieldstral reads yours in natural language, modifiable **without retraining**. The technical report (**arXiv:2607.25857**, July 28, 2026) quantifies the cost of this choice: fine-tuning on public data alone = **61.1% F1** on policy adaptability; **4.4 million contrastive pairs** generated by an LLM (the same content rewritten to violate a policy but not its sibling policy) = **+23.3 points**; **91.3%** after merging three checkpoints. Characteristics: **3.8B actual parameters** (the "3B" in the name rounds down), **Ministral 3** base + **Pixtral** vision encoder, **12 languages**, **16 GB of VRAM in BF16**, **Apache 2.0**. Text performance: **84.9% average F1**, on par with **GPT-OSS-Safeguard-20B** (seven times larger), ahead of **Qwen3Guard-8B** (84.0) and far ahead of **LlamaGuard-4-12B** (69.1). **A caveat raised by the author himself**: *all these figures come from Mistral, on test sets selected by Mistral, and no third-party evaluation existed as of August 6*. The note's structuring thesis is an **opposition of topologies**: at **Anthropic**, the guardrail lives **in the weights** and the publisher arbitrates who is exempt from it (**Claude Fable 5** public with safety measures / **Claude Mythos 5** without, reserved for approved cyberdefenders of **Project Glasswing**, June 9, 2026); at **Mistral**, the guardrail **sits outside the model** — a separate, open, self-hostable component, whose policy belongs to the deployer. Explicit customer alignment (ministry of the Armed Forces, BNP Paribas, French and Luxembourg government administrations). The note closes on a **setback documented in three points**: **auditability** (binary output, no reasoning trace, while the deployer inherits the burden of justification under an AI Act audit), **robustness** (the first chapter of Voltaire's *Treatise on Tolerance* classified as "calls for violence" by a tester on the Hacker News thread — a mention/endorsement confusion), **availability** (as of August 6: no billed endpoint on La Plateforme, no official Ollama). Three deployment rules to close.
**Didier Girard** — auteur de la note · publiée sur son compte X. Écrit ici en **analyste de doctrine industrielle** plutôt qu'en testeur : il n'a pas déployé le modèle · il croise une **audition parlementaire** (Mensch, 13 mai) · un **lancement produit** (Shieldstral, 4 août) · un **rapport technique** (arXiv, 28 juillet) et un **contre-exemple concurrent** (Anthropic, 9 juin) pour montrer qu'ils forment une position cohérente. Deux marqueurs de posture : il **borne explicitement la valeur des chiffres** qu'il cite (aucune évaluation tierce) et il **termine par des règles opérationnelles** — l'analyse doit sortir avec sa traduction en décisions de déploiement.