Glossary
The vocabulary buyers, auditors and architects use when they evaluate how AI work actually gets done. Each definition is written in general terms first, then links to the page that goes deeper.
The layers of an enterprise software stack and where work actually runs.
The layer above your systems of record that turns intent into completed work across them. It runs the process that crosses the ERP, CRM, contract repository and HR system, applies the policy that spans them, and records what was decided and why.
What is a System of Action?An application that owns authoritative data for one domain and enforces its own permissions on that data. An ERP owns the financial record, a CRM owns the customer record, an HRIS owns the employee record.
System of Action vs System of RecordThe interface layer where people ask questions and receive answers, such as chat assistants, search front ends and collaboration tools. It captures intent; it does not own the data or run the process to completion.
System of Action vs System of RecordThe runtime that carries a request through every step needed to finish it, including calls into other systems, waits on people, retries and exceptions. Distinct from the retrieval layer, which finds and summarizes information.
Platform architectureSoftware that indexes enterprise content and answers questions about what exists. It reads across systems and returns context. It does not complete work in those systems.
System of Action vs System of RecordThe VeroTX reasoning engine. It routes each task across available models based on cost, latency, capability and data sensitivity, and consolidates agent decisions inside a running WorkStream.
VeroCortexThe VeroTX conversational interface. People start and follow WorkStreams in chat, complete inline forms, and approve or reject steps without leaving the conversation.
VeroliThe integration framework that lets a platform read from and write to existing business systems under scoped, revocable credentials. In VeroTX, connectors are built in the connectors studio and can be created by the people who own the process.
StudiosBring your own cloud. Deployment of the platform into the customer's own cloud account so data residency and network boundaries stay under customer control.
Deployment pathHow agent work is bounded, approved, versioned and proven after the fact.
Software that interprets a goal, chooses steps toward it, and calls tools or systems to carry those steps out. Unlike a fixed script, it decides what to do next at run time.
AI agent platforms, explainedAn agent scoped to a single task or prompt, such as drafting an email or summarizing a document. It ends when the task ends and holds no state across a longer business process.
AI agents vs workflow automationAn agent whose permissions, tools and data access are limited to one stage of a defined process, so it cannot act outside the step it was assigned.
Procurement agentsA process run where every step is checked against the rules in force before it is allowed to proceed, and every step taken is recorded. Governance is enforced by the engine that runs the work, not by the interface that requests it.
Where agent governance should liveA structured business process, such as procurement intake or vendor onboarding, expressed as stages with owners, entry conditions and exit conditions.
WorkStream PlaybooksThe versioned definition of a WorkStream: its stages, the agents scoped to each stage, the rules that apply, and the approvals required. A run is bound to the Playbook version it started under.
WorkStream PlaybooksA numbered, reviewable revision of a Playbook. Changing a process creates a new version rather than editing the rules an in-progress run is executing under.
Playbook version historyA point in a process where work stops until a named person approves it. The rule that triggers the stop, the person who cleared it, and the time it was cleared are all recorded.
WorkStream PlaybooksA design in which specified decisions require a person to act before the process continues, rather than a person reviewing the outcome after the fact.
AI governance for enterprise workflowsThe immutable record of a run: every step, decision, approval and system call, each bound to the Playbook version, the agent or person responsible, and a timestamp. Written by the runtime rather than added on top.
Execution LedgerA step whose outcome follows fixed rules and is identical every time for the same input, such as a tolerance check or an approval threshold.
Platform architectureA step where a model produces a judgment rather than a fixed result, such as classifying a request or matching a line item. Probabilistic steps are bounded by deterministic checks and approvals around them.
Platform architectureThe ability to reconstruct, after the fact, what an AI system did, under which rules, on whose authority, and with what inputs, from records the system produced while it ran.
Execution LedgerThe VeroTX usage unit. Credits are consumed by agent actions taken inside a WorkStream, so cost tracks work completed rather than seats.
PricingProcess vocabulary that shows up in procurement, finance and audit conversations.
Value lost at the points where work passes between people, teams or systems: delays, rekeyed data, missed terms and requests that stall between owners.
Handoff leakageThe end-to-end process from a purchase request through sourcing, contracting, purchase order, receipt, invoice matching and payment.
ProcurementA control that compares the purchase order, the goods receipt and the supplier invoice before payment is released, and routes any discrepancy for review.
Procurement capabilitiesCompletion of a transaction end to end without manual intervention, with exceptions routed to people instead of the whole volume passing through a queue.
Finance OpsA control requiring that no single person or account can both initiate and approve the same sensitive transaction.
AI governance for enterprise workflowsInternal controls over financial reporting required of US public companies under the Sarbanes-Oxley Act, including evidence that approvals happened and that access to financial processes is restricted.
Financial servicesKnow your business. The verification of a supplier or partner entity, including registration, ownership, sanctions screening and risk checks, before it is transacted with.
Procurement capabilitiesPrepared by client. An auditor's request for documents and evidence supporting a transaction or control during an audit.
Finance OpsEngineering change order. The controlled request to change a released design, bill of materials or specification, along with the reviews and approvals that change requires.
Engineering Ops