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 17 — Domain Training and Affinity

Domains are labels you supply

Domains and subdomains organize probes by the questions you want to ask. They do not establish that the model has learned the same categories. Keep domain definitions stable when comparing runs and check coverage when one category contains fewer or less varied probes.

Separate the outcome sources

Trainer-reported train and holdout metrics come from your code. Probe metrics come from IRIS™'s fixed inspection inputs. Answer-span probe accuracy differs from whole-text token accuracy, and neither is automatically an independently sampled held-out estimate. Name the source when sharing a plot.

Training affinity

Positive measured gradient affinity means sampled domain gradients point in similar directions; negative affinity means opposition under that measurement. It does not establish that tasks always transfer or conflict, or that changing their sampling weights will improve training.

Read uncertainty intervals, sample coverage, and missing-data statements. An absent measurement is not zero affinity. Do not generalize a relationship beyond the probes, groups, frames, and measurement conditions it covers.

Representation comparisons

Domain spectra, overlap, composition, and subspace views describe different aspects of how labeled probes are represented. A domain map can use a chosen reference or a declared pooled reference; the reference is part of the measurement, not a neutral origin that every comparison shares.

Single-domain runs cannot support a between-domain comparison. Category views also need categories distinct from domains to add a separate reading. Read the stated applicability rather than treating a pooled fallback as a second independent result.

Form a testable question

Use an observed separation, overlap, or opposition to select examples and frames for closer review. Record any proposed interpretation as a hypothesis and test it against held-out behavior or a controlled experiment. The chart alone does not identify a semantic mechanism or a causal circuit.

Domain maps — Figures 4.18–4.20

These views compare domain organization using a polar map, a domain similarity matrix, and distance from the all-probe average by layer. Read the displayed frame, grouping, reference, and selected layers together. A change of reference or frame changes the comparison; a domain label is supplied by the probe curriculum, not an inferred semantic identity.