Corvair Virtual Worker: a hub and engine for agentic workers

The idea

A worker is a definition, not a prompt.

Everything a new colleague receives in their first week, expressed so a runtime can execute it. Two workers as different as an enterprise seller in Singapore and a property assistant in Jakarta differ in their definition and their knowledge, not in the engine that runs them.

badge

Identity & remit

Who it is, and what it may do

Name, personality, voice, its own workspace account and number, the remit it is accountable for, and the boundary of its authority.

stairs

Objectives

An ordered ladder, not a goal

Each rung a materially different outcome, pursued in order, with standing intelligence objectives captured alongside without displacing them.

school

Methodology

A discipline it practises

Loaded as governed content rather than written into logic, so your methodology becomes the worker's method without a code change.

fact_check

Outcome contract

A structured record, every time

What was agreed, at what confidence, by what path, plus the intelligence gathered, populated only from evidence and never invented.

lightbulb

Why this matters commercially. A virtual worker is bought against a headcount line rather than a software line, and it is judged against what a competent person in that role produces. That is why the objective ladder, the outcome contract and the improvement loop matter more than raw model quality.

**One conversation, fully inspectable.** The transcript as it happens, the objective ladder it is climbing, the structured record forming as it goes, and the fully composed prompt that produced the behaviour. **A worker you cannot inspect is a worker you cannot improve.**

Hub, engine, adapters

Build the hard part once. Plug in the rest.

The engine is where the difficult, general work lives: objective execution, memory, conversation policy, scoring and governance. Everything that varies by customer, channel or system is an adapter behind a stable interface.

The engine

The part nobody should build twice

Context assembly before a conversation starts, working memory during it, turn by turn conversation policy, objective ladder execution, tool mediation, and a structured outcome written back at the end. Channel agnostic and language agnostic by construction, so the same worker logic drives a phone call, a message thread and a web chat in any supported language.

stairsObjective & task engine memoryThree tier memory record_voice_overVoice and model profiles layersSix layer prompt ruleGuardrails and escalation

Explore the enginearrow_forward

hub Adapters

Everything that varies

Channels, systems of record, tools and skills, all behind one interface. Adapters carry protocol knowledge and never own conversation state.

The adapter modelarrow_forward

groups Workers

A growing family

Each a definition plus a knowledge scope plus a set of grants. Commissioned, not built. The Inside Sales Assistant and the Property Assistant both run on it today.

See the familyarrow_forward

Architecture at a glance

Nine planes, and governance runs through all of them.

Trust, provenance, consent and the audit trail sit in the data path rather than as a layer applied afterwards. Two capabilities cut across all nine: the intelligence system, being the relationship graph that gives a conversation something to be about, and the work lists built on top of it.

Plane 1Worker Runtime

Context assembly, working memory, engine and voice selection, language following, conversation policy, ladder execution, tool and skill mediation, intelligence write back.

Plane 2Objective & Task Engine

Ladder definitions, standing objectives, task assignment, the flow library, the event bus with priority conflict resolution, and the goal seeking loops.

Plane 3Omni-Channel Fabric

One conversation thread per contact spanning every channel, with preference tracking, automatic fallback, voicemail handling and graceful degradation.

Plane 4Knowledge, Assets, Tools & Skills

The Knowledge Substrate, the methodology library, the collateral a worker delivers, the MCP tool surface, and a governed skill library.

Plane 5Systems of Record

Bidirectional integration with whatever the business runs on, with provenance on every write and nothing silently overwriting a human entered field.

Plane 6Governance & Trust

Eight checks in the request path of every outbound action: jurisdiction, consent basis, suppression, channel hours, frequency, capture level, disclosure and rules of engagement. Plus immutable audit and warrants over worker actions.

Plane 7Calibration

Every conversation scored, low scores logged and classified, prompt revisions proposed, approved by a person, promoted only after regression.

Plane 8Control Plane

Worker definitions and templates, rosters and assignment, supervision, approval queues, the request board, tenancy and configuration.

Plane 9Telemetry, Cost & Entitlement

The trace and metric spine, per interaction cost capture and budget enforcement, entitlements and caps, and feature by role authorisation.

What makes it different

Seven things that are hard to copy.

Anyone can connect a model to a phone line. The combination below is what separates a demonstrator from a system a regulated institution will actually deploy.

stairs

Objectives that hold

An ordered, procedural ladder where a lower rung may only be attempted once the higher one is genuinely closed off, with anti-degradation rules so a maybe is never recorded as a yes.

forum

One thread, every channel

A conversation can start in a message, move to voice for the complex part, and return to text for scheduling, as a single thread. Most tools lock a conversation to the channel it began on.

workspace_premium

Governed knowledge underneath

Answers grounded in a trust scored substrate with citations and a premise chain, so what the worker asserts can be traced to what it was actually told.

insights

It measurably improves

Every conversation scored, failures classified, revisions proposed and approved by a person, and nothing promoted until it passes regression against a saved suite.

verified_user

Compliance in the platform

The engine sits in the request path of every outbound action, fails closed on an unanswered dimension, and has no route around it. We supply the engine, the schema and the record. You or your partner supply every value and the signature. Corvair never signs.

groups

It works inside a team

It can extend the capacity of named sellers, or hold a remit of its own from the business as an internal service provider, or both. What it may commit is a versioned setting you can narrow at any moment, and when its goals disagree the arbitration is explicit rather than assumed. How goals and delegation work.

hub

It builds a picture, not a log

Organisations, people, positions, budgets and how they connect, held as a graph. A role can exist before you know who fills it, and a champion who changes employer keeps their relationships. See the intelligence system.

receipt_long

Cost you can see

Per interaction cost capture, budgets that act rather than merely report, and a projected cost per worker per month that a buyer can hold against a salary.

The workers

Two roles running, on one runtime.

Both are voice first and real time, multilingual, regulated, and commercially measurable. They share the engine, the outcome contract model, the scoring arithmetic and the compliance engine. What differs is the application layer, the ladders and the contracts.

Available support_agent

Inside Sales Assistant

Enterprise sales development

Navigates organisations, follows referral chains, detects initiatives before they become formal procurements, qualifies against your methodology, and books meetings with the right people. Eight ladders, one outcome contract, eleven standing objectives.

Explore inside salesarrow_forward

Available home_work

Property Assistant

Sales and rentals

Answers enquiries, qualifies buyers and applicants, arranges accompanied viewings, wins market appraisals, reports back to owners, and establishes intention on tenancies ending. Fifteen ladders across five outcome contracts.

Explore propertyarrow_forward

In design psychology

Domain Coach

Human development

The first sales coach in the building with the data. Deal guidance, call preparation, longitudinal skill analysis, and rehearsal against a simulated contact.

How coaching worksarrow_forward

grid_viewThe full worker family play_circleSee a worker in action hubIntelligence and work lists groupsTeam, goals and events

Built on the substrate

The knowledge layer is not something you have to build.

Corvair Virtual Worker consumes the Corvair Knowledge Substrate rather than reimplementing a knowledge base. That is where a worker's competence comes from, and where its answers get their provenance.