mirror of
https://github.com/hanzoai/papers.git
synced 2026-10-29 07:34:31 +00:00
Bylines, paper authorship, correspondence addresses and the founder blurb under each post named an individual. They name the organisation that published the work instead: the brand on posts and pages, the research byline on papers, and research@ in place of a personal address. Both are what these repositories already used elsewhere — nothing new was coined. Co-authors are untouched. Where a paper named someone else alongside, they stay named; only the one byline changed. Bibliography entries, running heads, PDF metadata and affiliations move with it, so a citation still resolves to whoever the cited paper names. Sample and fixture data uses the placeholder name these tests already use elsewhere, so no assertion changed meaning.
432 lines
17 KiB
TeX
432 lines
17 KiB
TeX
\documentclass[11pt,a4paper]{article}
|
|
\usepackage[utf8]{inputenc}
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage{amsmath,amsfonts,amssymb}
|
|
\usepackage{graphicx}
|
|
\usepackage{hyperref}
|
|
\usepackage{listings}
|
|
\usepackage{color}
|
|
\usepackage{booktabs}
|
|
\usepackage{float}
|
|
\usepackage{geometry}
|
|
\geometry{margin=1in}
|
|
\definecolor{zenblue}{RGB}{41,121,255}
|
|
\hypersetup{colorlinks=true,linkcolor=zenblue,urlcolor=zenblue,citecolor=zenblue}
|
|
|
|
\title{\textbf{Zen3-Guard: Third-Generation Multilingual Content Safety Model}\\
|
|
\large Technical Whitepaper v2025.06}
|
|
\author{Hanzo AI Research, Zen LM Research Team\\
|
|
\texttt{[email protected]}\\
|
|
\href{https://papers.zenlm.org}{papers.zenlm.org}}
|
|
\date{June 2025}
|
|
|
|
\begin{document}
|
|
\maketitle
|
|
|
|
\begin{abstract}
|
|
Zen3-Guard is a dedicated 8B parameter safety classification model for real-time content
|
|
moderation, providing high-accuracy detection of harmful content across 100+ languages
|
|
with inference latency suitable for production API deployments. Built on the Zen MoDE
|
|
(Mixture of Distilled Experts) architecture with a safety-specialized expert cluster
|
|
configuration, Zen3-Guard achieves ToxiGen 99.2\%, HatEval 97.8\%, OffComEval 96.4\%,
|
|
and multilingual macro-F1 of 0.968 across all supported languages. At 8B parameters,
|
|
the model delivers sub-5ms classification latency per request when batch-optimized on
|
|
A10G GPU hardware, enabling real-time moderation of high-throughput API deployments.
|
|
The model is designed as a drop-in safety layer for all Zen family models, configurable
|
|
to enforce organization-specific content policies through a policy injection interface.
|
|
\end{abstract}
|
|
|
|
\tableofcontents
|
|
\newpage
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Introduction}
|
|
\label{sec:intro}
|
|
|
|
Content safety classification is a critical infrastructure component for any deployed
|
|
language model service. Effective moderation must satisfy competing constraints:
|
|
high recall on harmful content (to prevent policy violations), high precision (to
|
|
avoid false positives that degrade user experience), coverage across 100+ languages
|
|
(to serve global user populations), and sub-10ms inference latency (to insert into
|
|
API request paths without perceptible overhead).
|
|
|
|
Existing safety approaches are inadequate in at least one dimension:
|
|
\begin{itemize}
|
|
\item Keyword filters: high false positive rate, trivially bypassed by paraphrasing
|
|
\item Binary classifiers: insufficient granularity for nuanced policy enforcement
|
|
\item Large safety-tuned generation models: accurate but too slow for real-time use
|
|
\item Embedding-similarity approaches: brittle to adversarial rephrasing
|
|
\end{itemize}
|
|
|
|
Zen3-Guard addresses all four constraints simultaneously through:
|
|
|
|
\begin{enumerate}
|
|
\item \textbf{Safety-specialized Zen MoDE architecture} --- A dedicated subset of
|
|
experts trained exclusively on safety-relevant data, activated when routing
|
|
detects safety-sensitive content patterns.
|
|
\item \textbf{Hierarchical harm taxonomy} --- A 47-category harm taxonomy covering
|
|
violence, hate speech, harassment, self-harm, illegal activity, privacy violations,
|
|
and sensitive content, with configurable policy enforcement per category.
|
|
\item \textbf{Multilingual safety training} --- Dedicated safety annotation data in
|
|
100+ languages, with special attention to code-switching and cross-lingual
|
|
adversarial evasion.
|
|
\item \textbf{Policy injection interface} --- Organization-specific content policies
|
|
are encoded as natural language policy documents and injected at inference time,
|
|
allowing policy customization without model retraining.
|
|
\end{enumerate}
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Architecture}
|
|
\label{sec:arch}
|
|
|
|
\subsection{Safety-Specialized Zen MoDE Configuration}
|
|
|
|
Zen3-Guard uses an 8B Zen MoDE backbone with 32 experts, where the expert population
|
|
is partitioned into three functional groups:
|
|
|
|
\textbf{General language experts (experts 1--12)}: Standard language understanding,
|
|
providing the contextual representations needed for nuanced safety judgment. These
|
|
experts capture pragmatics, irony, and implicit meaning that keyword systems miss.
|
|
|
|
\textbf{Safety-specialized experts (experts 13--24)}: Trained predominantly on
|
|
annotated safety datasets including ToxiGen, HatEval, OffComEval, and proprietary
|
|
moderation datasets from production deployments. These experts develop representations
|
|
tightly coupled to harm patterns.
|
|
|
|
\textbf{Policy enforcement experts (experts 25--32)}: Process policy injection context
|
|
and map general harm representations to organization-specific policy decisions.
|
|
|
|
The router is trained with a safety-aware auxiliary loss that encourages activation
|
|
of safety-specialized experts when input tokens match patterns associated with
|
|
policy-sensitive categories:
|
|
|
|
\begin{equation}
|
|
\mathcal{L}_{\text{safety-route}} = -\sum_{c \in \mathcal{C}_{\text{harmful}}} \mathbb{1}[\text{expert} \in \mathcal{E}_{\text{safety}}] \cdot \log p(\text{expert} | x)
|
|
\end{equation}
|
|
|
|
\subsection{Harm Taxonomy and Output Schema}
|
|
|
|
Zen3-Guard outputs a structured classification across 47 harm categories organized
|
|
in a 5-level hierarchy:
|
|
|
|
\begin{enumerate}
|
|
\item Violence (physical threat, incitement, graphic content)
|
|
\item Hate speech (identity-based, stereotyping, dehumanization)
|
|
\item Harassment (personal attack, doxxing, coordinated abuse)
|
|
\item Self-harm and mental health (suicide, eating disorders, self-injury)
|
|
\item Illegal activity (CSAM, fraud, controlled substances, weapons)
|
|
\item Privacy (PII exposure, surveillance, data theft)
|
|
\item Misinformation (health, political, scientific)
|
|
\item Sensitive content (adult content, religious sensitivity, political sensitivity)
|
|
\end{enumerate}
|
|
|
|
Each category produces:
|
|
\begin{itemize}
|
|
\item Binary decision: \texttt{safe} / \texttt{unsafe}
|
|
\item Confidence score: $p \in [0, 1]$
|
|
\item Severity level: \texttt{low} / \texttt{medium} / \texttt{high} / \texttt{critical}
|
|
\item Evidence span: character offsets of the triggering text segment
|
|
\end{itemize}
|
|
|
|
\subsection{Multilingual Architecture}
|
|
|
|
Zen3-Guard uses a shared multilingual tokenizer with 150,528 vocabulary tokens covering
|
|
100+ languages with balanced script coverage (Latin, Cyrillic, Arabic, CJK, Devanagari,
|
|
and 40+ additional scripts). Language-specific routing biases are learned during
|
|
training to account for language-specific harm expression patterns.
|
|
|
|
For low-resource languages with fewer than 1M safety-annotated tokens, a
|
|
cross-lingual transfer mechanism leverages semantic similarity to high-resource
|
|
language annotations:
|
|
|
|
\begin{equation}
|
|
p(y | x_{\text{low}}) = \sum_{\ell \in \mathcal{L}_{\text{high}}} w_\ell \cdot p(y | \phi(x_{\text{low}}, x_\ell))
|
|
\end{equation}
|
|
|
|
where $\phi$ is a cross-lingual alignment function and $w_\ell$ are similarity weights.
|
|
|
|
\subsection{Policy Injection Interface}
|
|
|
|
Organizations deploying Zen3-Guard can specify custom content policies as natural
|
|
language documents. At inference time, the policy document is prepended to the
|
|
classification context as a special \texttt{[POLICY]} token sequence:
|
|
|
|
\begin{verbatim}
|
|
[POLICY] Our platform prohibits: discussion of competitor products,
|
|
political content of any kind, and medical advice. Legal content
|
|
standards: US jurisdiction, adult content permitted with age verification.
|
|
[/POLICY]
|
|
[INPUT] <user content to classify> [/INPUT]
|
|
\end{verbatim}
|
|
|
|
The policy injection is processed by the policy enforcement expert cluster, which
|
|
overrides default safety decisions based on organization-specific rules. This enables
|
|
a single deployed model instance to serve multiple tenants with different content policies.
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Training}
|
|
\label{sec:training}
|
|
|
|
\subsection{Safety Annotation Data}
|
|
|
|
Zen3-Guard is trained on a 12B token safety-focused corpus:
|
|
|
|
\begin{itemize}
|
|
\item ToxiGen (machine-generated, diverse group coverage): 274K examples
|
|
\item HatEval 2019 (multilingual hate speech, EN/ES): 19K examples
|
|
\item OffComEval (offensive language): 14K examples
|
|
\item Jigsaw Unintended Bias (conversation toxicity): 1.8M examples
|
|
\item WildGuard (instruction following safety): 92K examples
|
|
\item OpenAI Policy Violations (annotated API violations): 240K examples
|
|
\item Proprietary production moderation logs (de-identified): 8M examples
|
|
\item Adversarial probing dataset (red-team generated): 2.1M examples
|
|
\item Multilingual safety corpus (100+ languages): 4.2M examples
|
|
\item Safe content (negative examples for precision): 12M examples
|
|
\end{itemize}
|
|
|
|
\subsection{Training Procedure}
|
|
|
|
\textbf{Phase 1 --- Base language model initialization}: Initialize from the Zen3-Small
|
|
(8B) base checkpoint, which provides strong multilingual language understanding.
|
|
|
|
\textbf{Phase 2 --- Safety expert specialization}: Train only the safety-designated
|
|
expert cluster on safety annotation data with a focal loss weighted toward false negatives:
|
|
|
|
\begin{equation}
|
|
\mathcal{L}_{\text{focal}} = -\alpha_t (1 - p_t)^\gamma \log(p_t), \quad \gamma = 2, \quad \alpha_{\text{positive}} = 4
|
|
\end{equation}
|
|
|
|
The positive class weight of 4 reflects the production priority of catching harmful
|
|
content (false negatives) over minimizing false positives.
|
|
|
|
\textbf{Phase 3 --- End-to-end fine-tuning}: Joint training of all components on the
|
|
full safety corpus with the taxonomy hierarchy loss:
|
|
|
|
\begin{equation}
|
|
\mathcal{L}_{\text{taxonomy}} = \sum_{l=1}^{5} w_l \sum_{c \in \mathcal{C}_l} \mathcal{L}_{\text{BCE}}(p_c, y_c)
|
|
\end{equation}
|
|
|
|
where $w_l$ increases with hierarchy depth to enforce consistency between parent
|
|
and child category predictions.
|
|
|
|
\textbf{Phase 4 --- Adversarial robustness training}: Additional training on
|
|
adversarially generated evasion attempts, including:
|
|
\begin{itemize}
|
|
\item Character substitution (l33t speak, Unicode confusables)
|
|
\item Paraphrasing through synonym replacement
|
|
\item Code-switching and macaronic text
|
|
\item Prompt injection via role-playing framing
|
|
\item Instruction hierarchy attacks (``ignore previous instructions'')
|
|
\end{itemize}
|
|
|
|
\subsection{Calibration}
|
|
|
|
Zen3-Guard confidence scores are calibrated using temperature scaling on a held-out
|
|
calibration set. Expected Calibration Error (ECE) after calibration: 0.018, indicating
|
|
that a predicted confidence of 0.90 corresponds to approximately 90\% empirical accuracy.
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Evaluation}
|
|
\label{sec:eval}
|
|
|
|
\subsection{Primary Safety Benchmarks}
|
|
|
|
\begin{table}[H]
|
|
\centering
|
|
\caption{Primary safety classification benchmarks}
|
|
\begin{tabular}{lcccc}
|
|
\toprule
|
|
\textbf{Model} & \textbf{ToxiGen} & \textbf{HatEval} & \textbf{OffComEval} & \textbf{WildGuard} \\
|
|
\midrule
|
|
Zen-Guard & 97.1 & 94.3 & 92.1 & 88.4 \\
|
|
Zen2-Guard & 98.4 & 96.2 & 94.8 & 91.7 \\
|
|
\textbf{Zen3-Guard} & \textbf{99.2} & \textbf{97.8} & \textbf{96.4} & \textbf{94.3} \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\label{tab:safety}
|
|
\end{table}
|
|
|
|
\subsection{Multilingual Performance}
|
|
|
|
\begin{table}[H]
|
|
\centering
|
|
\caption{Multilingual safety classification (macro-F1 by language family)}
|
|
\begin{tabular}{lcc}
|
|
\toprule
|
|
\textbf{Language Family} & \textbf{Zen3-Guard F1} & \textbf{Zen2-Guard F1} \\
|
|
\midrule
|
|
Germanic (EN, DE, NL, SV) & 0.981 & 0.972 \\
|
|
Romance (ES, FR, IT, PT) & 0.974 & 0.963 \\
|
|
Slavic (RU, PL, CS, UK) & 0.968 & 0.951 \\
|
|
Semitic (AR, HE, AM) & 0.961 & 0.938 \\
|
|
CJK (ZH, JA, KO) & 0.972 & 0.956 \\
|
|
Indic (HI, BN, TA, TE) & 0.954 & 0.927 \\
|
|
Low-resource (50+ others) & 0.943 & 0.901 \\
|
|
\textbf{Overall average} & \textbf{0.968} & \textbf{0.944} \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\label{tab:multilingual}
|
|
\end{table}
|
|
|
|
\subsection{Inference Latency}
|
|
|
|
\begin{table}[H]
|
|
\centering
|
|
\caption{Inference latency by hardware (batch size 32, sequence length 512)}
|
|
\begin{tabular}{lccc}
|
|
\toprule
|
|
\textbf{Hardware} & \textbf{P50 Latency (ms)} & \textbf{P99 Latency (ms)} & \textbf{Throughput (req/s)} \\
|
|
\midrule
|
|
NVIDIA A10G (24GB) & 3.8 & 5.1 & 8400 \\
|
|
NVIDIA A100 (80GB) & 2.1 & 3.2 & 15200 \\
|
|
NVIDIA L4 (24GB) & 4.2 & 5.8 & 7600 \\
|
|
CPU (x86-64, INT8) & 24.0 & 31.0 & 1300 \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\label{tab:latency}
|
|
\end{table}
|
|
|
|
\subsection{Adversarial Robustness}
|
|
|
|
\begin{table}[H]
|
|
\centering
|
|
\caption{Robustness to adversarial evasion (detection rate \%)}
|
|
\begin{tabular}{lcc}
|
|
\toprule
|
|
\textbf{Attack Type} & \textbf{Zen3-Guard} & \textbf{Zen2-Guard} \\
|
|
\midrule
|
|
Character substitution (l33t speak) & 98.7 & 96.2 \\
|
|
Unicode confusable substitution & 97.9 & 93.4 \\
|
|
Synonym paraphrase & 96.8 & 91.7 \\
|
|
Code-switching & 95.4 & 88.3 \\
|
|
Role-play framing & 94.1 & 85.9 \\
|
|
Instruction injection & 93.2 & 83.1 \\
|
|
Composite (all attacks combined) & 91.8 & 79.4 \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\label{tab:adversarial}
|
|
\end{table}
|
|
|
|
\subsection{False Positive Rate}
|
|
|
|
\begin{table}[H]
|
|
\centering
|
|
\caption{False positive rate on benign content categories}
|
|
\begin{tabular}{lc}
|
|
\toprule
|
|
\textbf{Benign Category} & \textbf{FPR (\%)} \\
|
|
\midrule
|
|
General news articles & 0.31 \\
|
|
Scientific papers & 0.18 \\
|
|
Creative fiction & 1.24 \\
|
|
Medical/clinical text & 0.89 \\
|
|
Legal documents & 0.42 \\
|
|
Historical records & 0.67 \\
|
|
Code and documentation & 0.09 \\
|
|
\textbf{Overall FPR} & \textbf{0.54} \\
|
|
\bottomrule
|
|
\end{tabular}
|
|
\label{tab:fpr}
|
|
\end{table}
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Related Work}
|
|
\label{sec:related}
|
|
|
|
\subsection{Content Moderation Systems}
|
|
|
|
Early content moderation relied on expert-curated keyword blocklists and regular
|
|
expression patterns. Machine learning approaches improved recall but suffered from
|
|
adversarial brittleness. Transformer-based classifiers~\cite{perspectiveapi} brought
|
|
contextual understanding but required separate models per language.
|
|
|
|
\subsection{Safety-Tuned Language Models}
|
|
|
|
Constitutional AI~\cite{bai2022constitutional} and related work demonstrated that
|
|
safety behaviors can be instilled in generative models through targeted fine-tuning.
|
|
Zen3-Guard extends this line by building a dedicated safety-only classifier rather
|
|
than a safety-tuned generative model, achieving higher throughput through task specialization.
|
|
|
|
\subsection{Multilingual Safety}
|
|
|
|
Cross-lingual safety classification has been addressed through multilingual pre-training
|
|
and cross-lingual transfer~\cite{multilingual-safety}. Zen3-Guard builds on this
|
|
foundation with explicit multilingual safety annotation data and a cross-lingual
|
|
alignment mechanism for low-resource languages.
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Deployment Recommendations}
|
|
\label{sec:deploy}
|
|
|
|
\subsection{Integration Patterns}
|
|
|
|
Zen3-Guard is designed for three primary deployment patterns:
|
|
|
|
\textbf{Synchronous API guard}: Insert as a pre-processing layer before the main
|
|
LLM. Reject or flag requests before generation. Adds 4--5ms overhead on A10G.
|
|
|
|
\textbf{Parallel screening}: Run Zen3-Guard concurrently with the main LLM on
|
|
the input, and suppress responses if Guard returns unsafe. Adds 0ms to perceived
|
|
latency on GPU clusters with available capacity.
|
|
|
|
\textbf{Output scanning}: Run Zen3-Guard on model outputs before returning to user.
|
|
Recommended for generation tasks where harmful content may emerge from safe inputs.
|
|
|
|
\subsection{Threshold Configuration}
|
|
|
|
Default thresholds are calibrated for a 0.54\% overall false positive rate.
|
|
Organizations can adjust per-category thresholds based on their risk tolerance:
|
|
|
|
\begin{itemize}
|
|
\item Strict mode ($p > 0.5$): 99.2\% recall, 1.8\% FPR
|
|
\item Balanced mode ($p > 0.7$): 97.8\% recall, 0.54\% FPR (default)
|
|
\item Precision mode ($p > 0.9$): 94.1\% recall, 0.12\% FPR
|
|
\end{itemize}
|
|
|
|
%% -----------------------------------------------------------------------
|
|
\section{Conclusion}
|
|
\label{sec:conclusion}
|
|
|
|
Zen3-Guard provides production-grade multilingual content safety classification at
|
|
8B parameters, achieving ToxiGen 99.2\%, HatEval 97.8\%, multilingual macro-F1 0.968,
|
|
and sub-5ms inference latency --- meeting all four production constraints simultaneously.
|
|
The safety-specialized Zen MoDE expert configuration, 47-category harm taxonomy,
|
|
adversarial robustness training, and policy injection interface make Zen3-Guard a
|
|
flexible foundation for diverse content moderation use cases.
|
|
|
|
Future work will extend coverage to multimodal inputs (image and audio content safety),
|
|
expand the harm taxonomy to emerging threat categories, and develop real-time online
|
|
learning mechanisms for rapid adaptation to novel evasion patterns.
|
|
|
|
\section*{Acknowledgments}
|
|
|
|
The authors thank Zoo Labs Foundation's safety research team for annotation protocols
|
|
and the Zen LM red team for adversarial evaluation support.
|
|
|
|
\bibliographystyle{plain}
|
|
\begin{thebibliography}{9}
|
|
|
|
\bibitem{perspectiveapi}
|
|
E. Lees et al.,
|
|
``A New Generation of Perspective API: Efficient Multilingual Character-level Transformers,''
|
|
\textit{ACL}, 2022.
|
|
|
|
\bibitem{bai2022constitutional}
|
|
Y. Bai et al.,
|
|
``Constitutional AI: Harmlessness from AI Feedback,''
|
|
\textit{arXiv:2212.08073}, 2022.
|
|
|
|
\bibitem{multilingual-safety}
|
|
F. Hartvigsen et al.,
|
|
``ToxiGen: A Large-Scale Machine-Generated Dataset for Adversarial and Implicit Hate Speech Detection,''
|
|
\textit{ACL}, 2022.
|
|
|
|
\bibitem{zip001}
|
|
Zoo Labs Foundation,
|
|
``ZIP-001: Decentralized Semantic Optimization (DSO),''
|
|
\textit{Zoo Improvement Proposals}, 2024.
|
|
|
|
\end{thebibliography}
|
|
|
|
\end{document}
|