Skip to content
InovagioInovagio

Virtual EmployeesRole workers

Virtual Employees that ask before they act.

Every plan is checked against your rules before it runs. Anything outside them waits for a named person.

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 10, live work, for the example company Harlow Distribution: an invoice held under rule AP-7 is waiting for an AP specialist because the vendor’s bank details changed by email from an unknown sender. It shows the rule, the change, the new account’s last digits and the amount, with Vendor confirmed: continue and Hold payment.

What Virtual Employees do

Virtual Employees are Inovagio’s workforce: workers that plan and do real work across your systems, check every plan against your rules, and pause for a person when policy says so.

  • Plans checked first

    Before a step runs, the plan is checked against your rulebook and policies. A plan that breaks a rule never starts.

  • Breaks the work down

    Virtual Employees split each goal into tasks and hand them to specialist Virtual Employees in sequence or in parallel, choosing among eight reasoning strategies and recording why.

  • People stay in charge

    Approvals are steps in the run itself. The approver, the decision and the reason become part of the record.

  • Works in your systems

    Reads documents, calls your tools and writes to your systems under the identity and permissions you set.

How a task is aligned before it runs.

Every task is checked against its department’s rules and the company’s goals, policy and risk. Anything outside policy goes to a named person.

How a task is aligned before it runsA task arrives from a request, email, trigger or event and is queued per department and priority in MNEMOS. Department agents check it against department rules, then a company gate checks it against goals, policy and risk with Phylax. Anything outside policy goes to a named person. Ready tasks run on Nexus and Ergon in a sandbox, an auditor checks the result, and the Evidence and Cost Ledgers record it. Corrections update the rules.GOAL ALIGNMENT · EVERY TASK TRACES UP TO A COMPANY GOAL1. Task arrivesA request, email,trigger or event2. QueuedPer department andpriority, in MNEMOS3. DepartmentAgents and skillscheck department rules4. Company gateGoals, policy andrisk · Phylax5. RunsNexus and Ergon,Sandboxed runtime6. CheckedAuditor, Evidenceand Cost LedgersOutside policyA person decidesNamed approver,reason on the recordApprovedCorrections update the rules, so the next task is right first time

Virtual Employees at work

In the App at step 10: Go live, one kind of case at a time.

  • Rule AP-7 held invoice INV-21877: the bank details changed by email, from an unknown sender.
  • The person sees the rule, the change, the new account and the amount.
  • Continue once the vendor confirms, or hold the payment.
The Inovagio App at step 10, live work, for the example company Harlow Distribution: an invoice held under rule AP-7 is waiting for an AP specialist because the vendor’s bank details changed by email from an unknown sender. It shows the rule, the change, the new account’s last digits and the amount, with Vendor confirmed: continue and Hold payment.
In live work, an invoice whose bank details just changed waits for a person, with the rule and the reason attached.

Inside Virtual Employees

The views Virtual Employees give the people who run them, on sample data from Inovagio’s example companies.

The claims operations go-live page in the Inovagio App for Fernbrook Casualty, an example company with example data. A claim file is waiting for the adjuster. The page shows how many files need a person and how many were done today, and lists each file that needs a person with the rule that sent it there.

Virtual Employees › Today: a department at go-live, with how many cases were done today, how many need a person, and the rule that sent each one. Sample data from Inovagio’s example companies.

The products that make up Virtual Employees.

Virtual Employees

  • NexusAgent network and schedulingBuild, schedule and run governed agents anywhere your work happens.
  • ErgonWorkflow engineDurable workflows where agents, people and systems each do their step.

What you get with Virtual Employees

  • Building an agent

    A governed runtime that is part of the platform.

  • Before an action

    A policy check blocks a step that breaks a rule before it happens.

  • Human approval

    A named approval step, recorded in the ledger.

  • Who owns and runs it

    You own the rulebook, and your team or ours runs it.

Everything Virtual Employees do, by area.

Work intake

  • Per-area task queues in MNEMOS
  • Direct, email and role-based routing
  • Scheduled and event-driven work
  • Refinement: is the definition of done testable?
  • Escalation and returned work
  • Outcomes fed back to the knowledge graph

Governance

  • Permission modes, ceilings and an immutable floor
  • Plan-level approval
  • Blast-radius risk signal
  • Decision record for every gated action
  • Hash-chained audit on every step
  • Tenant bound from the signed-in identity

Virtual Employees

  • Virtual Employees and people in one workforce model
  • Lifecycle: create, deploy, pause, resume, retire
  • Health, success rate, latency and cost per Virtual Employee
  • SLA thresholds per Virtual Employee
  • Area models trained for a department’s work
  • Skills packs for business tasks

Portable Virtual Employees

  • Package a Virtual Employee as a signed, portable file
  • Ed25519 signing and verification
  • AES-256-GCM encrypted sections
  • Declarative Virtual Employee definition language
  • Import and export between environments

What Virtual Employees replace

Virtual Employees do the work of these, inside one platform with one identity, one policy and one record:

  • Agent framework assembled in-house
  • Robotic process automation scripts
  • Shared inbox and ticket triage by hand
  • Approval chains run in email and chat

The controls Virtual Employees bring

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

  • Security

    Virtual Employees act under the permissions you grant, never more.

  • Governance

    Every plan is checked against your rules before it runs; anything outside policy waits for a person.

  • On the record

    Each step records the rule it followed and who approved it.

  • Monitoring

    Every run is traced end to end in Panoptes.

  • Cost per task

    Routine work moves to small models you own, and the cost of every task is shown.

Virtual Employees in your industry

Every industry runs the same ten steps, so Virtual Employees do the same job in each, on that industry’s own work.

For developers: Virtual Employees at a glance

Runs on
One workstation, a business server, or hosted for you
System of record
MNEMOS for tasks, queues, runs and audit
Models
Origin: local open models or a chosen frontier model
Approvals
Inline, headless over the control channel, or on approval cards
Control verbs
stop · kill · pause · redirect · inform · approve · deny · dispatch
Package format
.ve: signed, encrypted, portable
Interfaces
Web console, desktop app, CLI, product API

Request the developer editionSee the architecture

Virtual Employees in the platform.

Where Virtual Employees fits

One platform
  1. Agent HarnessAgent harness

    Inovagio CLIInovagio DesktopWeb ChatInovagio SDK

  2. OpsisExperience layer

    FolioMorphe

  3. Virtual Employees (this layer)Virtual 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 Virtual Employees fits

Questions

Virtual Employees questions

Can a Virtual Employee pay or send something on its own?

Only where your policy allows it. Anything outside policy pauses for a named approver, and the approval is part of the record.

Which models does it use?

The model you choose: open models on your own hardware through Origin, or a frontier model, behind one API.

How do you know what an agent did?

Every step is written to a hash-chained ledger: what it read, which rule applied, who approved it and what it cost.

Guides and posts on Virtual Employees

See Virtual Employees on one of your workflows.

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