OFFLINE SIMULATION · NO LIVE IRIS OR MODEL
Investigate a routing incident
Explore authored synthetic examples. No agent, verifier, IRIS production, real approval, or delivery runs in this simulation.
- Target
- Checking…
- Runtime and model
- Checking…
- Connection
- Checking…
How this workflow is checked
Request → IRIS Interoperability → native AI Hub and scoped evidence tools → agent decision → recorded Diagnostic or Review branch → independent readback and verification.
A passing check confirms the demonstrated synthetic contract. Applying a change is a separate replay, plan and approval workflow; it is never authorized by an agent recommendation alone.
Define the task
Investigation
Execution scope & limits
Waiting for backend state.
Inspect the result
Activity and evidence
No investigation started.
No run selected.
No branch receipt recorded.
Inspect tool inputs and evidence
No evidence recorded.
Reviewed procedures
Learning review
Reusable procedures have their own evidence, applicability and review. Their acceptance is separate from a verified investigation.
Checking the learning store…
Teaching example · fixture only
This offline example is separate from the gated native teaching feature. It does not inspect an IRIS session.
A recorded hop tells you where a message was seen.
This example shows a recorded hop in a synthetic trace. The session groups messages; each message has its own ID.
Delivery is unverified when the example has no destination receipt. A recorded hop alone does not prove delivery.
Next, inspect the last recorded message and look for a receiving-system receipt.
IRIS terms and source
Session ID, message ID, message header and Visual Trace. This common-concept reference does not establish Build 154-specific behavior.
InterSystems Visual Trace documentation (2026.2)