IRIS Ops Studio v1.2.1 — Native Logs and Guided Wallet Policy

IRIS Ops Studio 1.2.1 adds two focused workflows to the safety-first management portal for InterSystems IRIS 2026.2.

New in 1.2.1

• Bounded native IRIS logs (read-only). An optional IRIS-hosted extension reads paginated records from messages.log, SystemMonitor.log, and alerts.log into Incident Timeline. Missing and partial sources are identified explicitly. It accepts fixed source identifiers, not arbitrary file paths, and requires IRIS authentication plus %Admin_Operate:U and package-namespace read access.
• Guided wallet access policy. For an existing non-system collection, review and change only EditResource and UseResource. The workflow shows both fields, re-reads immediately before PUT, blocks stale or malformed state, requires target-bound confirmation, and verifies both fields with a fresh GET. Secret values are never requested.
• Clearer evidence. Updated screenshots and documentation separate live-IRIS observations from Safe demo fixtures, and state the exact test boundaries.

Verification

The final source archive passed 103/103 JavaScript tests and 20/20 Linux native-reader tests after extraction. Both workflows were exercised against disposable IRIS Community 2026.2 installations, including restricted-account denial, bounded native-log paging, a real stale wallet preview that sent no PUT, and desktop/mobile visual checks. See the 1.2.1 validation record for the precise scope and fixture cleanup.

Source ZIP SHA-256: 62ADDEB9115C08A0C6FE27E435908B4F40CB88E3DBF108C8FABED5C0BB8532C7.

Scope and limits

The core portal remains a same-instance browser client; the native-log endpoint is optional and GET-only. IRIS privileges are the server-side authorization boundary. This release does not claim a portal-wide server-enforced safe mode, atomic wallet writes, a complete downstream user-impact graph, or journal/interoperability log decoding. The existing three videos demonstrate earlier workflows and remain labeled as such.