IRIS Chronos

Verify Chronos. Watch the 62-second walkthrough · Install on IRIS 154 · Inspect the native proof

When a shipment is interrupted, a retry can create a duplicate. IRIS Chronos checks the original attempt before preparing one recovery. An IRIS AI Hub agent interprets the customer’s preference inside an Interoperability production. Deterministic checks enforce cost, timing, inventory and prior acceptance. An authenticated Operator approves the exact recovery.

Try the case. Open queue_inventory and ask why the workflow selected B when A cost less. A costs 3 units, but its seven-minute queue outlasts six minutes of inventory validity. B costs 6 and fits the budget of 8. Ask about the original rejection or whether the chat can approve B. The answer cites case records and directs approval to the Operator.

Verified in IRIS 154. Six synthetic cases ran on bundle 463. Bundle 467 repeated the main case from a fresh installation, with three questions in one English conversation. A direct Reader request to prepare an approval was denied. Operator confirmed B once. When the test withheld the response after acceptance, reloading recovered the same operation, attempt and receipt. The submission preserves the tested application and installer code. Six-case matrix

Inspect the native trace. IRIS Visual Trace shows the stored decision response, token counts and SDK call interval for the recorded E1 example. A separate native adapter test replayed the original identifier and returned its stored decision without a second inference. View recorded Visual Trace · Download the MP4 without signing in

Run locally. The tested setup uses IRIS AI Hub Community 2026.3.0AI.154.0 x64, Docker Compose, Windows PowerShell and local Qwen through Ollama. Obtain the licensed IRIS image separately. All cases and destinations are synthetic. The walkthrough is a recording from the earlier 407r2 run.