Copyright © 2026 Saccadic LLC · Patent pending.

Browse chapters
  1. Release NotesChanges by version
  2. Chapter 1What IRIS Is and Is Not
  3. Chapter 2The IRIS Data Model
  4. Chapter 3How IRIS Measures
  5. Chapter 4Safe Interpretation and the First 15 Minutes
  6. Chapter 5Dashboard Overview
  7. Chapter 6Installation
  8. Chapter 7Configuration
  9. Chapter 8Build the Model Spec and Probe Set
  10. Chapter 9Minimal Tracker Integration
  11. Chapter 10Launch the Bench and Verify Capture
  12. Chapter 11Runtime Control, Signals, Metrics, and Logs
  13. Chapter 12Integration Patterns by Model Family
  14. Chapter 13Distributed Training
  15. Chapter 14Artifacts, Reports, Export, and Security
  16. Chapter 15Troubleshooting
  17. Chapter 16Whole Model and Layer Structure
  18. Chapter 17Domain Training and Affinity
  19. Chapter 18Attention-Head Diagnostics
  20. Chapter 19MoE Expert and Router Diagnostics
  21. Chapter 20Facets and Emergent Pathways
  22. Chapter 21Gradient Residuals, Stability, Curvature, and Update Efficiency
  23. Chapter 22Adaptive Cadence and Event Detection
  24. Chapter 23CLI Reference
  25. Chapter 24Configuration-Key Reference
  26. Chapter 25API Reference
  27. Chapter 26File and Schema Reference
  28. Chapter 27Glossary and Concept Index
  29. Chapter 28The Flow Map
  30. Appendix ADiagnostic Availability Matrix
  31. Appendix BLLM Prompt Library
On this page

Chapter 19 — MoE Expert and Router Diagnostics

Experts and routing are different readings

On a supported mixture-of-experts capture, inspect both which experts receive traffic and what the recorded representation or motion readings show for those experts. Routing weight, effective dimensionality, and parameter motion answer different questions.

The expert indices are the model's own identities. A shared expert or dense path is labeled separately when the architecture has one. Do not infer that two nodes with a similar domain mix are the same expert, or that an expert belongs exclusively to a domain because that domain currently dominates its traffic.

Read shares with their denominator

A routing or weight-motion share is relative to the quantity and coverage named by the figure. It is not a loss contribution or a causal importance score. Read whether the figure covers all experts, a displayed subset, a particular domain, or a particular measured interval.

Missing and restricted captures

Per-expert views need supported expert/router captures. Some model wrappers need their integration to expose those captures; other architectures have no routed experts at all. The Bench distinguishes unavailable data from architectural non-applicability. Resource limits can also restrict which experts or frames a view covers.

Use the captions and availability notes before comparing experts across time or runs. A route not measured, a measured zero, and a link omitted from a drawing are different states. The Flow Map makes those distinctions particularly important.

Useful comparisons

Place changes in routing beside trainer-reported outcomes, domain readings, and run interventions. A stable accuracy curve does not imply that routing or internal structure is unchanged. Conversely, reorganization alone does not show that generalization improved or that a particular circuit formed.