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 24 — Configuration-Key Reference

Bench settings

The Bench reads ~/.iris/iris-bench.cfg. Supported launch preferences include [server] port, [launch] open_browser, and remembered [tree] positions. Let the UI write tree selections unless you have a reason to edit them by hand. An illustrative preference file is:

[server]
port = 8765

[launch]
open_browser = false

Use --port N for a launch-specific port preference and --no-open to suppress browser opening. Read the actual startup address rather than assuming the preferred port was available.

Tracker settings and live controls

~/.iris/iris-tracker.cfg supplies host-wide tracker preferences. Use only keys supported by your installed version. Unknown or unusable tracker keys can refuse startup; a misspelled setting is not silently a valid setting. Use the run's iris.cmd for supported live controls such as interval, adaptive bounds, sensitivity, and dryrun. See Chapter 11.

Capture coverage can be reduced when resources are constrained. Read the frame's mode and missing-channel reasons. A manual mode cannot force the instrument to capture beyond what it can support, and changing a resource setting does not manufacture data already omitted from a bundle.

Butler and derived expressions

~/.iris/iris-butler.cfg supplies relay defaults; a run's iris.cfg is a Butler-specific override. It is not a per-run Bench or tracker configuration. Saved User-tab expressions live in ~/.iris/derived_metrics.toml and retain their definitions and provenance for later runs.

Configuration boundaries

Keep credential-bearing configuration private. The Bench has no password; network policy controls viewing. Writes require localhost on the Bench machine or a supported SSH port-forward as your own account; see Chapter 10. For precedence and its exceptions, see Chapter 7.