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 12 — Integration Patterns by Model Family

Two routes into IRIS™

Supported model families can use an architecture spec and the normal model integration. A declared architecture uses a customer-supplied measurement adapter and explicit measurement groups. Choose the route that matches the model's actual structure; a familiar model name is not a substitute for correct dimensions, module paths, and probe tokenization.

Model-family questions to resolve

Family Check before a run
Decoder-only transformer Layer paths, attention head counts, tokenizer, padding, and answer-span definitions.
Encoder-only transformer Input masks and the model's scoring objective; next-token interpretations are not automatically appropriate.
Encoder-decoder Encoder and decoder structure, input/target handling, and which representations are being inspected.
Mixture of experts Whether the integration exposes the routing and expert captures needed by the requested views.
Vision, recurrent, state-space, or convolutional models A supported integration or declared adapter; transformer head/expert charts do not become applicable merely by supplying labels.

Use the model-family recipe supplied with your IRIS distribution for the specific wrapper and version. Validate a short run before scaling up. A recognizable forward signature does not establish that every diagnostic is supported on that route.

Declared architectures

With model_type: "declared", the adapter defines the measurement groups and captures. The labels belong to your adapter; do not present them as transformer heads or routed experts unless those structures actually exist. Preflight the adapter before a long job, and check the reported groups and availability in the first frames.

The manual distinguishes architecturally inapplicable views from supported but not-yet-emitted views. For declared runs, head/expert diagnostics are not made applicable by a switch. Some other families can be absent because their declared-route emission is not built yet. Read the availability reason rather than assigning a zero or assuming a configuration error.

Tokenizers and custom model behavior

The probe tokenizer must match the model. Supply masks and answer spans according to the public interface in Chapter 8. Keep custom measurement callbacks side-effect-free and independent of the training iterator. If a wrapper changes module paths, dimensions, or what its forward exposes, revisit the spec and adapter rather than reusing an old configuration unchanged.

Verify, then compare

Check a short instrumented run against your baseline and read logs for capture failures or missing channels. Compare like-for-like probes, objectives, and definitions across models. Absence of a channel is not evidence that the model lacks the property a different channel measures.