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 16 — Whole Model and Layer Structure

Start with the outcome curves

Keep trainer-reported training and held-out outcomes visible while reading internal structure. Aggregate accuracy can conceal differences between domains; probe metrics can differ from a held-out task measure. Check the source and unit of every curve before comparing its timing with another.

Read layer structure in context

Use k95, spectral entropy, spectral slope, and the spectrum together. They describe concentration and distribution in the measured representation. A layer with a lower k95 is not necessarily better, finished, unused, or less capable. The result depends on the probes and measurement available on that frame.

Basis rotation and principal-direction carry-over add a temporal view. An abrupt change locates an interval to inspect; its cause needs evidence from the run record and independent tests. Compare corresponding layers and actual captured steps, rather than screen positions in an animation.

Resources and provenance

A figure may state that it uses reduced or projected rows, a carried basis, or a restricted set of captures. Retain that provenance in interpretation and exported reports. Different capture modes can affect last digits or availability, so check those states before making a fine numerical comparison.

Older bundles can carry explicit reliability notices. In particular, the manual identifies affected Apple-silicon spectra recorded before the 20 October 2026 tracker fix. Read the notice attached to the actual run; an affected spectrum is not repaired by presenting it in a newer dashboard.

Questions to investigate

  • Which layers changed, and over which measured interval?
  • Is concentration changing together with orientation or motion?
  • Does the change appear on several probe domains or only one?
  • What did trainer-reported held-out outcomes do over that interval?
  • Did the run resume, change data, change optimizer, or change capture mode?

Those questions guide inspection. They do not turn an internal pattern into a universal predictor of generalization, quality, or failure.