Qwen3 MoE 35B Sovereign Judge v3 GGUF

--- license: apache-2.0 base_model: Qwen/Qwen3-30B-A3B tags: - gguf - judge - evaluation - quality-assurance - paraconsistent - multi-expert - reasoning - moe - mixture-of-experts - qwen3 - lora language: - de - en pipeline_tag: text-generation --- # Sovereign Judge 35B — GGUF v3 > **This model is not a general-purpose chat assistant.** > It is a specialised quality-assurance gate designed to evaluate, score, and arbitrate > the outputs of a Multi-Expert Orchestration (MoE) pipeline before they reach the user. ## What this model does The Sovereign Judge evaluates answers produced by multiple domain-expert LLMs running in parallel inside the [MoE Sovereign](https://github.com/h3rb3rn/moe-sovereign) orchestration system. Its three core responsibilities are: | Responsibility | Description | |---|---| | **Factual correctness** | Detects unsupported or contradictory specific claims (numbers, proper nouns, dates) against retrieved source material | | **Internal consistency** | Identifies logical inconsistencies across expert outputs in the same domain category | | **Conflict arbitration** | Resolves genuine contradictions between domain experts using paraconsistent Belnap-Dunn four-valued logic without logically collapsing on them | The Judge acts as the **last quality barrier** before a synthesised answer is returned to the user. When trust in the expert round is insufficient, it can block the response entirely or trigger a self-critique loop for refinement. --- ## Role in the MoE Sovereign pipeline ``` User query │ ▼ Planner (selects expert categories + tools) │ ▼ Expert LLMs (run in parallel, domain-specialised) │ ▼ Conflict Detection (paraconsistent registry built) │ ├─► Strategy A: auto-dismiss low-divergence conflicts (Jaccard < 0.5) │ └─► Strategy B: escalate safety-critical conflicts → Judge LLM │ ▼ Belnap-Dunn arbitration conflict_map + VERDICT │ ▼ Trust Score [0.0–1.0] ├── ≥ 0.65 → PROCEED (response sent) ├── 0.30–0.65 → PROCEED_WITH_ASSUMPTION (self-critique loop) └── < 0.30 → BLOCK (decision log, no response) │ ▼ Merger / Synthesis LLM │ ▼ User response ``` The Judge is invoked via `_invoke_judge_with_retry` — it is never on the hot path for simple, high-confidence single-expert queries (those take a fast path directly through the merger). --- ## Output schema When called for conflict arbitration, the...