IRIS Ops Studio 1.2.0 adds guided enable/disable for eligible non-system web applications, with a complete-configuration preview, fresh pre-write check, target-bound confirmation, and full readback. Management, default, ambiguous, and Ops Studio applications stay inventory-only.

• REST discovery: optional same-origin Management REST/OpenAPI documentation catalog. It does not invoke catalogued operations or forward the SysAdmin token; missing browser permission is shown explicitly.
• Safer operations: connection-bound previews, stronger task-completion verification, asynchronous Explorer and audit handling, credential-shaped redaction, uncertain-result reporting, and responsive mobile controls.
• Evidence: 84/84 automated tests. A fresh disposable IRIS Community 2026.2 image passed installation and authorization checks, plus authenticated Run/Suspend of an on-demand test task with independent IRIS readback. Access mutations and stale-preview blocking were checked on another disposable instance. The README and final validation report document the exact scope.

Limits: the portal remains a browser client; its safeguards do not impose a server-enforced read-only mode. IRIS authorization is the server-side boundary. In-place upgrade was not tested. The three existing videos remain linked; the newer two show 1.1.0 Safe demo workflows.

fix link to github repo

OpsDeck v0.1.0 — Initial Release
Initial public release of OpsDeck, an open-source operations console for InterSystems IRIS.
This release provides a unified read-only management workspace for IRIS operational information, including applications, access, security, tasks, system state, and logs.
Highlights:

• Live integration with authoritative InterSystems IRIS management APIs
• Web application and REST service discovery
• User, role, and resource visibility
• Security and credential metadata views with bounded field exposure
• Task, process, database, device, audit, and journal metadata views
• Evidence-oriented authoritative read-back verification
• Explicit read-only provider boundaries and secret-safe mappings
• Automated provider, server, and application tests
  OpsDeck v0.1.0 targets InterSystems IRIS Community Edition 2026.2. IRIS-native deployment and package-manager integration are being finalized as part of the v0.1 release line.

Initial Release

Initial Release

Version 0.2.0 adds a complete IPM package for Linux IRIS 2026.2 in USER: Python gateway, browser UI and authenticated runtime adapter. The foreground launcher accepts an existing authorized account and binds only to loopback. Installation creates no credentials, demo fixtures or background service. Ownership checks preserve conflicting installations and edited files.
The package was published to the official test registry. A separate clean consumer installed iris-fieldwork 0.2.0 solely from that registry, without a source copy. Four authenticated requests, four anonymous denials and eleven gateway routes passed, covering all six sections and 24 resource checks. The launcher and filesystem suite passed 31 tests on Linux.
IPM guide: https://github.com/jsdhwfmax/iris-fieldwork/blob/main/IPM.md
Validation: https://github.com/jsdhwfmax/iris-fieldwork/blob/main/runtime/ipm-validation.json
Release: https://github.com/jsdhwfmax/iris-fieldwork/releases/tag/v0.2.0
Please review this package for community-registry publication. The existing contest entry is already approved; this is a package/listing update. Production-registry availability and any bonus or prize remain unverified. This AI-assisted prototype is intended for a disposable local instance and is not a production security boundary.

IRIS Ops Studio 1.1.0 adds verifiable operations, access-management workflows, and Incident Timeline.

• Guided process, task, user-role, and role-resource changes now use before/after previews, target-bound confirmations, and fresh readbacks with explicit outcomes.
• Permission plans preserve unrelated grants, use documented mutable fields, and block stale previews before PUT.
• Incident Timeline combines IRIS audit records, task history, and the current browser session's operation journal, with source, severity, entity, actor, text, and correlation filters.
• The API explorer catalogs 34 official SysAdmin API v2 method/path pairs, up from 27 in 1.0.0. Demo simulations are labelled, unsafe or unsupported demo requests are declined, and credential-shaped content is redacted.
• 57 automated tests pass; four testable modules reached 98.98% aggregate line coverage in the final local run. Selected live workflows and the responsive interface were checked on disposable IRIS Community 2026.2 instances. The validation report records the exact scope.
• The long description now uses three Safe demo screenshots of the new 1.1.0 workflows; the existing video is identified as the original overview.
  These browser-side safeguards do not replace IRIS authorization. This release does not provide server-enforced per-tab read-only mode or a complete IRIS log aggregation stream. The existing video covers the original overview; the new workflows are documented in the updated README.

Initial Release

IRIS Maintenance Copilot 1.0.0

Initial competition release of IRIS Maintenance Copilot, an evidence-grounded industrial maintenance assistant built with InterSystems IRIS.

Included in this release

• Structured equipment and maintenance-event data stored in InterSystems IRIS
• Native IRIS vector storage and semantic retrieval with VECTOR_COSINE
• Lexical retrieval using %iFind.Index.Basic
• Hybrid retrieval using Reciprocal Rank Fusion (RRF)
• Grounded maintenance assessments generated from retrieved evidence
• Explicit evidence citations for possible causes and recommended checks
• Structured JSON output validation
• Hallucination safeguards for unsupported information
• Bounded retry handling for transient LLM provider failures
• Synthetic industrial-maintenance knowledge base and reproducible CLI demo

The application is intended as maintenance decision support and does not replace qualified inspection or a definitive technical diagnosis.

Initial Release

Initial Release

Initial Release

Initial Release

Initial Release

This is my entry to the ongoing programming contest.

This is an IRIS API Explorer. The API Is sorted into different categories and submit types. You can test out the API safely under different privileges. There is a rollback feature for any data changes or deletes.

Thanks!

Initial Release

Initial prototype for local InterSystems IRIS 2026.2. Six live management views, reviewed task/web/role/wallet operations, bounded audit and journal metadata searches, Docker Compose installation instructions and demonstration fixtures. Includes three public English-captioned walkthroughs. AI-assisted development; administrative test instance only. See README and DEMO.md for validation and limitations.

Listing update: adds the public interactive walkthrough at https://rafaorlando3.github.io/iris-relay/. The walkthrough uses fictional data only and needs no credentials. Source remains release 0.2.0, commit fe585681ed05719c202856d4dbf422a1685e5679, with 42 JavaScript and 6 Python tests passed and reversible live checks on IRIS 2026.2 ARM64.

Initial Release

JWT-related options, a bunch of fixes

fixed loader in iris.script

• dotenv installation instructions
• fix error "sqlalchemy.orm.exc.FlushError: Instance <Datayour_table_name at 0x288f1d06120> has a NULL identity key"

typo in REDAME fixed

Initial Release

Initial Release

Initial Release

Initial Release

Lots of security patches applied by GitHub dependabot.

Platform-independent Docker demo.

• Demo rebuilt on intersystemsdc/iris-community:latest-em: one container, no Web Gateway, no separate IPM install
• Same docker compose commands on Windows PowerShell, Command Prompt, WSL, macOS, and Linux; no bash scripts
• Demo runs in the USER namespace with Analytics enabled; cubes, pivots, dashboard, and warmed queries are built into the image
• Both test suites run from one command; GitHub Actions builds the image and runs them on every push
• Cache-warmer package unchanged; IPM module iris-bi-cube-cache-warmer 1.0.1
• Verified on InterSystems IRIS 2026.1 Community Edition

First public release.

• Query-frequency-ordered cache warming for IRIS BI cubes after builds and synchronizations
• Cube Manager Post-Build and Post-Synchronize integration with background, coalescing workers
• Dashboard and saved-pivot warming, including dashboard default filters
• Persistent run and per-query statistics, queryable via SQL
• IPM module iris-bi-cube-cache-warmer; install with zpm "install iris-bi-cube-cache-warmer"
• Docker Compose demo with two synchronized cubes, a dashboard, and tests
• Verified on InterSystems IRIS 2025.1 and 2026.1 Community Edition

Release notes — v1.0.4

dc.omniReRank v1.0.4 — Documentation fixes for setup on IRIS 2026

A docs-only patch resolving two setup blockers reported during the Open Exchange review. No code or public-API changes; existing installations do not need to be recompiled or reconfigured beyond the SSL step below.

🐛 Fixed

• %Embedding.Config.VectorDataType reference removed from setup examples. The property is not exposed on every IRIS 2026 build, and the previous INSERT INTO %Embedding.Config (…, VectorDataType, …) example failed at runtime on affected builds (Field '%EMBEDDING.CONFIG.VECTORDATATYPE' not found, or <PROPERTY DOES NOT EXIST> in ObjectScript). The example now uses only the portable minimum columns (Name, Configuration, EmbeddingClass, VectorLength, Description); VectorDataType is documented as build-dependent and set via property assignment when your build exposes it.
• sslConfig now correctly documented as required for every HTTPS provider. Prior examples omitted the key, causing %Embedding.OpenAI.IsValidConfig to reject the config at %Save() time with "Invalid Configuration: 'sslConfig' not set". Every JSON example in the README — Installation, Configuration Reference, and Demo — now includes "sslConfig":"OmniHTTPS" at both the top level (for the embedding provider) and inside the rerank sub-block (for the reranker). The Configuration Reference table upgrades sslConfig from optional to required for every HTTPS provider (Cohere, Voyage, Jina); not used by Ollama.

✨ Improved

• New Installation step 4 walks the operator through creating a Security.SSLConfigs entry (OmniHTTPS) in %SYS before wiring configs. Only skippable when Ollama is the sole provider.
• Installation step 6 clarifies the consumption path. Engine.Rerank remains registered as [SqlProc], but this IRIS build's SQL result-set marshaller does not surface custom %SQL.CustomResultSet columns to callers of CALL dc_omniReRank.Engine_Rerank(...) from the SQL runner. The recommended path is the ObjectScript classmethod call followed by %Display() or %Next() iteration. Fully SQL-native surfacing is tracked as a follow-up.
• Demo section now uses the ObjectScript Search invocation instead of the SQL CALL (which returned SQLCODE=0 with zero rows displayed in SMP).

🧪 Validated

• 69 unit tests green against IRIS 2026 (no external services required — every provider path is mocked).
• End-to-end demo verified: 20 OpenAI embeddings + real Cohere reranker over three natural-language queries, results reordered as expected.

🔄 Upgrade notes

• From v1.0.x: No code migration needed. If you followed a previous README to wire your %Embedding.Config, verify your Configuration JSON contains "sslConfig":"<your-ssl-config-name>" at both levels. If your IRIS build did not require sslConfig before, your row still needs it for the reranker to work — this is enforced by %Embedding.OpenAI and every SaaS reranker path.

⚠️ Known limitations

• CALL dc_omniReRank.Engine_Rerank(...) from the SMP SQL runner or another %SQL.Statement returns SQLCODE=0 but does not display rows. Use the ObjectScript classmethod call. Fix scheduled for a subsequent release.
• HNSW vector indexes require a fixed LEN on %Vector columns — documented in the demo Catalog.cls (pinned at 1536 dims for OpenAI). Adjust LEN or drop the index if using an embedding model with a different dimensionality.

🙏 Thanks

• Dmitrij Vladimirov (Open Exchange review) — for catching the two setup blockers and the excellent bug-report quality that made them a five-minute fix.