Chapter 14 — Artifacts, Reports, Export, and Security
What a run contains
The .iris bundle is the primary diagnostic record. The run directory holds
the tracker log and runtime scratch files; the Bench keeps recomputable
analysis separately on the machine. Notes, recordings, and exported reports
are also model-inspection records to review before sharing.
Chapter 26 lists their roles.
IRIS™ does not require uploading full model weights to inspect a local bundle. That does not make every artifact non-sensitive: labels, architecture, training behavior, probe text or references, notes, and trainer-supplied signals can reveal information about the model and data. Review files before sending them to another person or an external AI service.
Bundles and exports
A compatible Bench opens diagnostic bundles automatically; no user-managed bundle key is required. Control access to the files rather than assuming their filename or format is an access boundary.
Use Export as PDF for a report and the Bench's AI export for structured discussion. Confirm which run and frames are included. Some exports are full-run summaries while an individual figure may name a particular frame; those are different scopes. When sharing a chart, keep its caption, units, coverage, and missing-data explanation with it.
Let your own assistant read a running job
IRIS supports read-only measurement access through MCP. A person enables the
Bench's MCP switch, then the assistant runs iris mcp on that machine as
the same login account, without sudo or a service account. It is off at
Bench startup and restart. With no assistant connected, MCP turns off after
15 minutes. After training ends, it also turns off when every connected
assistant has made no calls for 15 minutes. A silent connected assistant may
remain connected during an active run. --keep-alive does not keep MCP enabled. The assistant receives the measurement numbers
available through Export for your AI, never personal notes. IRIS does
not perform interventions on the assistant's behalf. Review what you share
with your chosen assistant and retain human control over training changes.
Butler export
The optional iris-butler relay forwards captured scalars to supported
experiment trackers such as W&B, TensorBoard, MLflow, or Aim. Configure its
destination and credentials according to the installed guide. A run's
iris.cfg is a Butler configuration and can override the global Butler
defaults. Treat destination credentials as secrets and review the fields
you are sending.
Network posture
The Bench has no password: anyone who can reach its port can view it.
Writes and control actions require localhost on the Bench machine or a
supported SSH port-forward through that machine's own SSH server as your
login account. Tailscale SSH forwarding is viewing-only. Restrict viewing access through network policy and use a
trusted, encrypted path. For the supported Tailscale workflow, use the
machine's Tailscale name and follow your installation's network guidance.
Licensing uses network access separately from the local dashboard. Follow
the installation and account instructions supplied with your distribution
and check current readiness with iris --license. Do not interpret local
bundle reading as a claim that every IRIS operation is offline.
Review before sharing or deleting
Check the run identity, notes, probe material, export scope, and recipient. Keep original captures when you need an audit trail. Read deletion confirmations carefully: stopping a Bench is different from deleting a recorded run, and an archived-run deletion is not reversible.
