Skip to content
InovagioInovagio

OpsisCard apps

Answers as cards your team can act on.

Approvals, documents, sheets and charts as card apps from approved templates, every value linked to its source.

We’ll spend 30 minutes with you on one of your workflows, and you don’t need to share any data.

The Inovagio App at step 8 for the example company Harlow Distribution: the AP manager approves how invoices look to reviewers, four cards each rendered on test cases with the fields it shows. The task itself is a decision card with Approve and Send back.

What Opsis does

Opsis is Inovagio’s display engine: agents answer with card apps, such as approvals, documents, sheets and charts, drawn from approved templates and never from generated code.

  • Approved templates only

    The agent names a card type from a validated catalog. Unknown types and raw HTML never render.

  • Every value has a source

    Numbers come from a data query, not model text, and link to the rows they came from.

  • Sensitive data stays masked

    Area and data class travel with the card, and masking happens before anything is drawn.

  • Same card on desktop, web and phone

    One engine draws the same card on desktop, web and phone, with no outside UI framework.

Every card is a governed contract.

Seven parts make up every card, and four checkpoints sit between the model and what a person sees.

Anatomy of a card

Alder Ridge Community Bank, an example company · a renewal waiting on documents

7 parts · 4 checkpoints
Part 1card/approval · chainfrom the validated catalog
Part 2Commercial lendingConfidentialTax ID 84-•••2219, masked
Part 3

“Get LN-3187 ready for review.”asked by the credit analyst

Loan file LN-3187 · credit decision

Part 4
Borrower
Harlow Supply Co.↗ row
Renewal type
Renewal with new money↗ row
2025 business tax return
Received↗ row
Interim statement, Sep 2026
Received↗ row
2024 business tax return
Requested↗ row
Part 5Confirm the returns requestReturn with a noteas Ravi Desai · recorded
Part 6

Why this card: renewal documents rule v2 · credit policy §3.2 · the plan in plain language · 3 sources

Part 7

receipt RC-41F7 · refreshed 2 min ago · loan file LN-3187, credit policy §3.2

Seven parts in every card

  1. Card type from a validated catalogThe agent names a card type. Unknown types or raw HTML never render.
  2. Sensitivity marksArea and data class travel with the card; masking happens before anything is drawn.
  3. The askThe question in the person’s own words stays attached to the answer.
  4. Data bindingEvery value comes from a MNEMOS query plan, not model text, and links to its rows.
  5. ActionsEach click is a write under the person’s identity; changes become tasks with oversight.
  6. ExplanationThe terms used, the plan in plain language and the sources, one tap away.
  7. ReceiptReceipt id, freshness and sources, so any answer can be audited later.

Four checkpoints before anything is drawn

  1. 1 · Agent

    Emits a card spec as data, never as interface code.

  2. 2 · Client

    Checks it against the validated catalog and the person’s permissions.

  3. 3 · MNEMOS

    Binds it to live data with the asker’s credentials, rows and fields masked.

  4. 4 · Renderer

    Draws it in WebAssembly, the same on desktop, web and phone.

The model decides what to show; the platform decides whether and how.

Alder Ridge Community Bank · Example company

Opsis at work

In the App at step 8: Sign off and verify.

  • Four cards, each rendered on test cases with the fields it shows.
  • The department head decides how invoices look to reviewers.
  • The task is itself a card: Approve or Send back, with its record.
The Inovagio App at step 8 for the example company Harlow Distribution: the AP manager approves how invoices look to reviewers, four cards each rendered on test cases with the fields it shows. The task itself is a decision card with Approve and Send back.
The department head approves the cards reviewers will decide on, each rendered on test cases.

Inside Opsis

The views Opsis gives the people who run it, on sample data from Inovagio’s example companies.

A decision card in the Inovagio App for Ashgrove Health Plan, an example company with example data. The rule owner is asked to approve a change to an enrollment rule. The card shows the rule before and after, notes that the person who proposed the change was blocked from approving it, and offers two choices: approve it or send it back.

Opsis › Decision card: a rule change on its decision card: what changes, why this person decides, a block that stops the person who proposed it from approving it, and the choices. Sample data from Inovagio’s example companies.

The products that make up Opsis.

Opsis

  • FolioDocuments and spreadsheetsOpen, edit and save office files where your agents work.
  • MorpheDiagrams, vector and 3DDiagrams, drawings and 3D parts that people and agents edit together.

What you get with Opsis

  • How answers arrive

    As card apps with the actions built in.

  • Safety

    Only reviewed templates, checked against the person’s permissions.

  • Trust in the numbers

    Every figure is bound to live data and linked to its rows.

  • Building screens

    One engine draws document, sheet and chart cards.

Everything Opsis does, by area.

Card kit

  • Validated card catalog
  • 19 standard templates: approval, task, inbox, KPI, workflow, incident and more
  • Data binding and repeaters
  • Forms that work without scripts
  • Charts: line, bar, area, candlestick
  • Grids, diagrams and documents

Data and apps

  • MNEMOS, sheet, document and connector sources
  • Time series with server-side downsampling
  • Sensor streams
  • Versioned apps with pages and navigation
  • Shared app state
  • Templates saved only after review

Security

  • Tenant bound from the signed-in identity
  • Classification floor on every card
  • Strict content security policy on the web
  • Every action authorized and audited
  • Untrusted files parsed under limits

Delivery

  • Server-rendered HTML with live partial updates
  • WASM in a worker
  • Native hosts through the C ABI
  • No third-party runtime dependencies

What Opsis replaces

Opsis does the work of these, inside one platform with one identity, one policy and one record:

  • Dashboard builder
  • Low-code internal app builder
  • Model-generated front-end code
  • Front-end framework plus component libraries

The controls Opsis brings

Every Inovagio product keeps the same five commitments, because regulated work needs all five at once.

  • Security

    Cards run in a sandbox with only the data the user may see.

  • Governance

    Every card type comes from a validated catalog and is checked against the person’s permissions before it renders.

  • On the record

    Approvals made on a card are part of the record.

  • Monitoring

    Card load and use are reported to Panoptes.

  • Cost per task

    One card engine for desktop, web and phone, instead of a front end per app.

Opsis in your industry

Every industry runs the same ten steps, so Opsis does the same job in each, on that industry’s own work.

For developers: Opsis at a glance

Surfaces
Web, desktop, iOS and mobile, microcontroller (by profile)
Engine
First-party C++ UI engine
Web delivery
Server-rendered HTML plus WASM islands
Data
MNEMOS, sensors, connectors
Classifications
Public through PHI
Accessibility
Semantic tree on every card; keyboard operable

Request the developer editionSee the architecture

Opsis in the platform.

Where Opsis fits

One platform
  1. Agent HarnessAgent harness

    Inovagio CLIInovagio DesktopWeb ChatInovagio SDK

  2. Opsis (this layer)Experience layer

    FolioMorphe

  3. Virtual EmployeesVirtual Employee layer

    NexusErgon

  4. SynesisKnowledge layer

    PerceptionMNEMOS

  5. OriginModel layer

    Inference ServerForge

  6. PhylaxTrust layer

    AuthInovagio SecretsGuard

  7. OperationsOperations

    PanoptesArchon

  8. Platform servicesPlatform services

    ServerAPI ManagementConnect

Where Opsis fits

Questions

Opsis questions

Can an agent draw anything it likes?

No. It can only name a card type from your validated catalog, and the client checks it against the person’s permissions before anything renders.

What does a click on a card do?

Each click is a write under the person’s own identity, and changes become tasks with oversight.

See Opsis on one of your workflows.

Every project starts with one workflow your people know well, measured against what it costs you today.