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 22 — Adaptive Cadence and Event Detection

Choose the sampling schedule

Fixed mode records at a configured interval. Adaptive mode can record more densely when the instrument detects change and relax toward a less frequent schedule at other times. These are sampling choices, not declarations that the model has learned, generalized, or failed.

Use the Bench controls or supported iris.cmd commands. The run must reach should_extract() or extract() for staged commands to be read.

echo "interval 500" > iris.cmd

That example pins the interval at 500 training steps. Choose a value suited to your workload and the temporal resolution you need; it is not a universal recommendation. Percentage settings depend on the declared total-step count.

Adaptive bounds and sensitivity

cutback <fast> <slow> sets the fast and steady-state bounds used by adaptive capture. In the Bench, review both interval boxes before committing a change. sensitivity <S> changes how readily the instrument records denser evidence: higher means more frames, lower means fewer. Its relationship to the number of frames is approximate, and a quiet run can remain quiet.

These controls affect measurement work and storage as well as temporal resolution. Measure overhead on the actual model and hardware. A denser capture is useful only when the observations it records help your question.

What a marker establishes

An event marker records an instrumentation decision or reported event. It does not identify a grokking event, causal circuit, optimizer failure, or generalization mechanism. Representation-motion telemetry and trainer outcomes remain different measurements. Their alignment is an observation to test, not a universal prediction rule.

Changes you make to the run can produce real changes in the readings: checkpoint resumes, optimizer changes, reinitialized weights, or a changed data pipeline. IRIS™ does not know the meaning of an intervention merely because it observed motion afterward. Keep a run note and interpret the event against that record.

Timing claims need cadence

When comparing a marker with accuracy or loss, report the relevant step labels, the sampling intervals, and the source of the outcome metric. Sparse captures bound the timing you can resolve. A visible animation between frames is not another measurement, and the mean-accuracy curve is not a substitute for per-domain evaluation.

Inspect the tracker log and the frame coverage when an event is recorded without a nearby plotted value. Do not invent a missing point or relocate a marker to make a proposed explanation look cleaner.