Skip to content
InovagioInovagio

NexusAgent network and scheduling

Build, schedule and run governed agents anywhere your work happens.

Agents work within a budget until a check confirms the goal is met, and hand work to each other securely.

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 6 for the example company Harlow Distribution: the AP manager chooses who handles exceptions and who gets alerts. It shows the four queues (Incoming, Ready to work, Done, Needs a person), the two people who work Needs a person on weekdays, and how they are told, each notice with one link to the task.

Where Nexus works

Schedules the work and hands it between workers (Nexus). These are the onboarding steps it works in, from your first decision to live work.

  1. Step 6 · BuildBuild the releaseRemoves: The black box.

How the ten steps work

What Nexus does

Nexus is Inovagio’s agent network and scheduler: it keeps every agent on its goal until a check confirms it is met, its budget runs out or a person decides. It runs the same governed work as a conversation, a workflow, a task or a scheduled job, and lets agents hand work to each other securely across machines and sites.

  • Agents that work together

    Agents find each other and hand off work, context and limited authority over encrypted, signed channels, across machines and sites, under the same policy and audit trail.

  • Goals held to a check

    A goal is started, paused, stopped and inspected through one governed control plane, and it closes only when a check confirms it is met, its budget runs out or a person decides.

  • Plans that break down and fan out

    Goals break into tasks, and independent tasks run in parallel while dependent ones run in order.

  • Conversations, workflows or jobs

    The same goal runs interactively, as a step in a workflow, as a queued task or on a schedule, and work can arrive by API, email or webhook, with its state kept in MNEMOS.

  • Agents built from skills

    Each agent is defined by its skills, tools, knowledge scope and model, with skills kept in a catalog in MNEMOS, and your own applications can host them.

  • People approve what matters

    Approvals sit inside goals and workflow runs, and the approver, decision and reason become part of the audit record.

Nexus at work

In the App at step 6: Build the release.

  • Four queues: Incoming, Ready to work, Done and Needs a person.
  • Two named people work Needs a person on weekdays.
  • Every notice carries one link to its task.
The Inovagio App at step 6 for the example company Harlow Distribution: the AP manager chooses who handles exceptions and who gets alerts. It shows the four queues (Incoming, Ready to work, Done, Needs a person), the two people who work Needs a person on weekdays, and how they are told, each notice with one link to the task.
Work moves through four queues, and the department head names who works Needs a person and who is told.

Inside Nexus

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

Nexus › Agent network: agents delegating, asking and handing off to each other. Sample data from Inovagio’s example companies.

Everything Nexus does, by area.

Goals and planning

  • Governed goal control: start, resume, stop, inspect
  • Autonomy ceiling per goal and per repository
  • Live goal progress and status projection
  • Goal sessions persisted and audited in MNEMOS
  • Grounded task decomposition and replanning
  • Parallel steps only where the work is independent
  • Contract-net task allocation among agents
  • Checks that each stage stays on its goal

Workflows, tasks and jobs

  • Workflow graphs, sub-workflows and simulation
  • Goals as workflow stages
  • Post-execution verification on every node
  • Cron triggers with time zones; interval, webhook and event triggers
  • Scheduled jobs and a task API with fenced leases and retries
  • Built-in workflows and a native visual workflow editor
  • Kill switch and cancellation
  • Risk scoring and what-if runs before a change

Agent network

  • Agent registration and discovery
  • AES-256-GCM channels with Ed25519 identity
  • Multi-hop routing with loop detection and TTL
  • Handoff protocol with context summarization
  • Delegation tokens with scope, depth and expiry
  • A2A task gateway and MCP gateway
  • Session budgets for tokens, calls and cost
  • Department, role and priority task routing on tenant topics

Control and surfaces

  • Human approval nodes and review queues
  • The same approval prompt in chat turns and goal runs
  • Approval and tools services over gRPC
  • Sandboxed execution in containers, OS sandboxes or git branch workspaces
  • Sealed, hash-chained audit of every action
  • CLI, Desktop and web chat faces with one admin console
  • Results rendered as Opsis card apps

What Nexus replaces

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

  • Agent frameworks assembled from libraries
  • Job schedulers and cron hosts for automation
  • Workflow orchestration engines
  • Task routing and work-queue systems
  • Separate approval tools bolted onto automation
  • Custom agent-to-agent messaging

The controls Nexus brings

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

  • Security

    Agents prove who they are, and every message between them is authenticated.

  • Governance

    Which agent may call which, with which skills, is set by policy.

  • On the record

    Every handoff, delegation and approval is on the record.

  • Monitoring

    Each agent, task and job is visible live, with its trace.

  • Cost per task

    Each task goes to the smallest model that meets its quality bar.

Nexus in your industry

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

For developers: Nexus at a glance

Faces
CLI (interactive and headless), Desktop app, web chat UI; one common admin console
Run modes
Conversation, goal, workflow, queued task, scheduled job
Embedding
C ABI core with Swift, Kotlin and Python bindings
Agent protocols
A2A task schema, Model Context Protocol, gRPC tools and approval services
Task intake
API, email and webhook ingestors; topic queues per tenant, department and priority
Security
AES-256-GCM channels, Ed25519 agent identity, scoped delegation tokens, fail-closed authorization
State
Goals, sessions, workflows, tasks, skills and audit stored in MNEMOS
Deployment
One machine, a team server with shared queues and worker processes, or the hosted cloud

Request the developer editionSee the architecture

Nexus in the platform.

Where Nexus fits

One platform
  1. Agent HarnessAgent harness

    Inovagio CLIInovagio DesktopWeb ChatInovagio SDK

  2. OpsisExperience layer

    FolioMorphe

  3. Virtual Employees (this layer)Virtual Employee layer

    Nexus (this product)Ergon

  4. SynesisKnowledge layer

    PerceptionMNEMOS

  5. OriginModel layer

    Inference ServerForge

  6. PhylaxTrust layer

    AuthInovagio SecretsGuard

  7. OperationsOperations

    PanoptesArchon

  8. Platform servicesPlatform services

    ServerAPI ManagementConnect

Where Nexus fits

See Nexus on one of your workflows.

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