OpsDeck

🚀 LIVE SAFE DEMO  ·  📦 PRIOR GITHUB RELEASE (v1.0.0)  ·  🛠️ INSTALL  ·  🐳 DOCKER QUICK START  ·  🧭 EVALUATOR GUIDE  ·  📊 CAPABILITIES

Evidence-first operations for InterSystems IRIS.
Observe live state · Rehearse changes · Forecast impact · Execute with authority · Verify what actually happened

OpsDeck 1.1.0 — Guided Contextual Learning is an open-source operations environment for InterSystems IRIS. It combines live management views, evidence-scoped verification, reviewed mutation workflows, semantic investigation, adaptive mobile UX, and bounded intelligence in one native IRIS-hosted interface.

Built for the InterSystems Programming Contest: Build Your Own Management Portal (2026).

v1.0.0: 117 IRIS operations exposed · 56 runtime-observed · 37 reproduced · 34 independently verified · 7 mutation endpoints · 12 qualified mutation workflows · 259 tests · 610,382 runtime-manifest bytes

Current main source: v1.1.0 — Guided Contextual Learning

OpsDeck v1.1.0 is integrated into main with optional, product-owned Learning ON/OFF, workspace orientation, mapped field Help, action explanations and receipt/state teaching. The Safe Demo consumes the same code and is published from main through the test-gated Pages workflow. See 1.1.0 release notes and baseline reconciliation.

The October 8 published-baseline observation records the Open Exchange listing as v1.0.1 (October 4, 2026) and its linked IPM archive registering opsdeck 1.0.0. Listing and package versions are distinct facts. Existing v1.0.0 release links, hashes and qualification results below remain historical.

The 1.1.0 source is merged, but a versioned GitHub/IPM/OEX 1.1.0 release has not been published. October 16 scoped acceptance records native IPM package build/install, an observed 1.0.0-registration → 1.1.0 upgrade, preservation, uninstall and restart checks. Authenticated guided-learning checks used exact 1.1.0 presentation assets on a separate quick-start backend registered as 1.0.0. This does not establish full authenticated browser qualification of the installed 1.1.0 package or full native RC PASS. Source merge, Safe Demo deployment and package publication are separate boundaries.

Why OpsDeck

Traditional admin interfaces often show state and leave the operator to infer what a change will do, whether it actually happened, and what evidence remains afterward.

OpsDeck makes that sequence explicit:

OBSERVE
   ↓
OPERATION REHEARSAL
   ↓
IMPACT FORECAST
   ↓
PLAN REVIEW
   ↓
CONFIRM
   ↓
EXECUTE
   ↓
AUTHORITATIVE READ-BACK
   ↓
VERIFIED RECEIPT
   ↓
SESSION LEDGER

The same semantics survive from desktop down to a 320-pixel mobile viewport. IRIS remains authoritative; OpsDeck does not invent a second source of truth.

90-second evaluator path

No IRIS instance or credentials are required for the public demo.

1. Open the Live Safe Demo and switch Learning ON.
2. Open Applications, select a web application, then try field Help and Walk through this workspace.
3. Review a read-only rehearsal and forecast to see why preparing an action is not executing it.
4. Switch Demo Access personas to see why visible objects do not automatically grant authority.
5. Open Evidence to distinguish scoped read-back from an executed, verified operation.
6. Turn Learning OFF for the compact operator view; try FX Studio or resize to mobile width.

The demo uses deterministic sanitized sample data and says so explicitly. It never substitutes sample records for a failed live IRIS read.

For the complete review path, see the Evaluator Guide.

What ships in 1.0

Operations and evidence

• Live IRIS identity, application, access, security, task, system, log, package, and evidence projections where admitted.
• Operation Rehearsal builds the canonical plan without dispatch.
• Impact Forecast projects target, pre-state, expected transition, authority, risk, reversibility, and likely service/user effect.
• Plan Review preserves the exact state being confirmed.
• Observe Only is enforced at the execution boundary, not merely by hiding buttons.
• Verified Receipt requires authoritative read-back at qualified mutation boundaries.
• Session Ledger projects current-session observations, plans, confirmations, receipts, findings, and refusals without creating a second history system.

SysAdmin reach

The source-generated inventory currently records:

Counts use HTTP method + canonical SysAdmin v2 path as the operation unit. A declared API contract does not become runtime proof merely because it exists in the OpenAPI document.

See Capability Inventory for the generated accounting and qualification boundaries.

Investigation and automation

• Native Embedded Python performs bounded fixed-log concept normalization.
• Native IRIS Vector Search provides source-linked semantic navigation over product-owned derived records.
• The generic SysAdmin explorer derives long-tail request structure from the official API specification while routing admitted mutations through the canonical planner/executor.
• Workflows compose existing OpsDeck operations rather than arbitrary code.
• Entity relationships remain tied to admitted Evidence.
• Candidate intelligence remains untrusted until the server reconstructs intent against authoritative state and normal policy/authority checks.

Adaptive UX

• Responsive semantic projection from desktop to one-thumb mobile operation.
• Command palette on desktop and thumb-accessible command surface on mobile.
• JSON/CSV export from already-admitted state.
• Multi-target identity and comparison semantics without pretending separate observations are one global truth.
• FX Studio separates base mode, material, effect intensity, and motion so customization remains modular while semantic status meanings stay invariant.

Compact by architecture

The qualified 1.0 runtime manifest is 610,382 bytes across 25 assets.

OpsDeck reached that size after expanding from 113 to 117 exposed operations and from 6 to 12 qualified mutation workflows. A later representation pass reduced the runtime below its pre-expansion size without removing those capabilities.

The point is not code golf. Shared semantic contracts carry planning, authority, evidence, targeting, and presentation so features do not each need their own copy of the same machinery.

Fun fact: the source logo is roughly 3.48× larger than the runtime manifest. The logo is staying. 🙂

Native installation

The exact qualified 1.0.0 archive is attached to the GitHub v1.0.0 release.

For the qualified artifact path, clone the tagged source and use the release archive from the GitHub release:

git clone https://github.com/KennethJSmithDev/OpsDeck.git
cd OpsDeck
git checkout v1.0.0

From the IRIS IPM prompt in %SYS, load the downloaded release archive:

load C:\path\to\opsdeck-1.0.0-rc.tgz

Then open:

http://127.0.0.1:52773/opsdeck/index.html

Adjust the HTTP port for the local instance.

The preserved release artifact is 154,243 bytes, SHA-256:

178bf6ea3809b023ed76a39ea313cfaf33ff3f5e91a5afbfc2627cadf3faf798

It passed fresh installation, an installed 0.8.0 → 1.0.0 update, uninstall with owned-state cleanup, and reinstall on the owned IRIS 2026.2 / IPM 0.10.8 qualification target.

Public IPM registry distribution of 1.0.0 is not claimed until independently observed. Until then, use the qualified GitHub release artifact rather than assuming zpm install opsdeck resolves 1.0.0.

See Native Installation for prerequisites, lifecycle boundaries, and recovery details.

Release qualification

The exact v1.0.0 tag points to qualified commit be35ed89c21e91079b0152ba4572f0700839b515.

Release qualification included:

• 259/259 regression tests;
• 25/25 shipped runtime assets matching source and authenticated native HTTP delivery;
• fresh archive installation and product-owned store initialization;
• connected native browser operation;
• Observe Only with zero dispatch;
• reversible native mutation with authoritative read-back and restoration;
• the same reviewed mutation flow at 320×568;
• native Embedded Python analysis and source-linked Vector Search;
• installed 0.8.0 → 1.0.0 update with bounded derived-state preservation;
• uninstall cleanup with unrelated IRIS/IPM state preserved;
• reinstall from the same preserved archive;
• staged source and archive privacy scans with zero high-confidence secret findings.

The full scope and limitations are recorded in 1.0 RC Qualification.

Built with the IRIS community

OpsDeck implements community-driven capabilities because they improve the product, not merely to collect contest checkboxes.

Current documented work includes reviewed IPM/Open Exchange package workflows associated with DPI-I-261, contextual IRIS learning assistance, and the read-only ObjectScript snippet library.

See Community Ideas Status for exact provenance, acceptance scope, and what is or is not being claimed.

Evidence semantics

OpsDeck deliberately keeps these states distinct:

• VERIFIED — independent evidence agrees with the displayed state.
• EMPTY — the authoritative provider returned a valid empty collection.
• UNAVAILABLE — the source could not provide a usable result.
• DENIED — the current identity lacks authority.
• FAILED — the provider reported failure.
• UNVERIFIED — the required qualification boundary has not been crossed.

Absence is not failure, and failure is not absence.

Security and authority

• Credentials are never committed to the repository.
• Native browser credentials remain in tab memory and are cleared by Sign out.
• Secret-bearing fields are not intentionally projected into generic views.
• Provider routes are explicit and bounded.
• Exact confirmation is bound to the reviewed plan.
• Observe Only blocks dispatch in the executor.
• Intelligence does not acquire authority merely by proposing an operation.
• Public IRIS management ports should not be exposed to untrusted networks.

See Security Policy.

Known boundaries

OpsDeck 1.0 does not claim universal support merely because the official API declares an operation.

Known release boundaries include:

• Task Description mutation returned HTTP 500 on the qualification target and remains excluded from dispatch admission and capability counts.
• The message-rotation probe returned a failed provider state; successful rotated-log retrieval is not admitted.
• Vector similarity is bounded concept navigation, not incident proof or a neural embedding claim.
• Vector concurrency and scale remain unqualified.
• External model inference is not required for core operation and remains outside the qualified 1.0 release claim.
• Qualification is scoped to the recorded IRIS 2026.2 disposable Docker target, identities, fixtures, and authority boundaries.
• Public-registry 1.0.0 installation remains unclaimed until independently observed.

Development

The preserved Node reference path remains useful for provider development and tests:

npm test
npm start

Open http://127.0.0.1:4173.

The application has no npm package dependencies; the reference server uses Node built-ins.

Documentation

• Evaluator Guide
• Native Installation
• Capability Inventory
• 1.0 Qualification
• Community Ideas Status
• Roadmap

Support

Use GitHub Issues for reproducible bugs and support requests. Never include passwords, tokens, private keys, or other secrets in reports.

License

OpsDeck is licensed under the MIT License.