VOICE — Virtuoso, OPAL, and LOAM as one open, loosely coupled context engine: any agent, any LLM, your data where it is.
Context Engine · Virtuoso · OPAL · LOAM

VOICE

Your Data. Your Know‑how. Any Agent. Any LLM.

Enterprise AI doesn’t need another data silo. It needs governed access to existing knowledge, persistent memory, and the ability to act.

VOICE (Virtuoso Open Interoperable Context Engine) combines Virtuoso, OPAL, and LOAM (Linked Open Agent Memory) into a loosely coupled infrastructure for AI agents. It doesn’t require enterprise data, AI agents, or LLMs to converge on a single proprietary platform: it connects them through open standards, shared semantics, and fine-grained governance.

VOICE architecture, explodedFive layers, top to bottom. AI agents and users: human users, AI agents, agent frameworks and LLMs. OPAL, the orchestration harness: natural language interface, skill and tool routing, LLM routing, and policy and governance. LOAM (Linked Open Agent Memory), an entity relationship graph collective of Linked Data: session, entity, task, trace, domain and preference graphs. Virtuoso, the multi-model DBMS and semantic harmonization layer: data federation, semantic harmonization, multi-model support and standards-based access. Enterprise Data Spaces, where your data remains where it is: relational databases, knowledge bases, filesystems, APIs and other sources. Enterprise Data SpacesYOUR DATA STAYS WHERE IT ISDATABASES · KNOWLEDGE BASES VirtuosoMULTI-MODEL DBMSSEMANTIC HARMONIZATION LOAMGRAPH COLLECTIVE · LINKED DATASESSION · ENTITY · TASK · TRACE OPALORCHESTRATION HARNESSNATURAL LANGUAGE · ROUTING AI Agents & UsersHUMANS · AI AGENTSFRAMEWORKS · LLMS
Architecture

Your enterprise already has Data Spaces. Your AI agents should work across them, not require their replacement.

Most AI-ready data platform strategies bring data, analytics, Knowledge Graphs, and AI capabilities closer together within one ecosystem. VOICE starts from a different premise: existing systems stay where they are, and agents reach them through open interfaces.

Federated data & semantic context
Relational tables, RDF Knowledge Graphs, and semantic data virtualization across databases, knowledge bases, filesystems, and APIs, without wholesale data duplication.
Intent-to-action orchestration
The harness that connects natural-language intent to executable queries and actions through loosely coupled Agents, Skills, and Tools, with cost-based LLM routing.
Persistent memory
Session histories, execution traces, entity relationships, decisions, and provenance, kept as reusable, machine-computable context.
The layers

What each layer holds

Read top to bottom: people and agents ask, OPAL orchestrates, memory recalls, Virtuoso harmonizes, and the Data Spaces stay authoritative.

AI Agents & Users

Who and what asks.

  • Human UsersAnalysts, domain experts, knowledge workers
  • AI AgentsClaude, ChatGPT, Grok Bot, Muse, and others
  • Agent FrameworksLangChain, AutoGen, CrewAI, custom harnesses
  • LLMsGPT, Claude, Gemini, Grok, Muse, and others

OPAL — Orchestration Harness

Turns intent into governed action.

  • Natural Language InterfaceIntent understanding and planning
  • Skills and Tool RoutingLoosely coupled Agents, Skills, Tools and Data Spaces
  • LLM RoutingCost-based model selection
  • Policy and GovernanceIdentity, ABAC, guardrails and audit

LOAM — Entity Relationship Graph Collective

Linked Data memory that accumulates across sessions.

  • Session GraphConversations, plans, goals
  • Entity GraphPeople, organizations, products, assets
  • Task GraphActions, tools, workflows
  • Trace GraphExecution traces, provenance
  • Domain GraphsSubject-specific knowledge (e.g., contracts, compliance)
  • Preference GraphUser and agent preferences
  • Additional graphsFurther domain-specific graphs

Virtuoso — Multi-Model DBMS

The semantic harmonization (virtualization) layer.

  • Data FederationConnect and query across heterogeneous Data Spaces
  • Semantic HarmonizationUnified view using RDF, ontologies and Linked Data
  • Multi-Model SupportRelational, RDF, property graph and files
  • Standards-Based AccessSQL, SPARQL, GQL, GraphQL, HTTP, ODBC, JDBC, WebDAV, etc.

Enterprise Data Spaces

Your data remains where it is.

  • Relational DatabasesPostgreSQL, MySQL, SQL Server, Oracle, etc.
  • Knowledge BasesWikis, document repositories, content management systems, enterprise knowledge bases
  • FilesystemsDocuments, PDFs, reports, logs, media
  • APIsMCP tools, OpenAPI services, REST/SOAP, enterprise applications
  • Other SourcesIoT, data lakes, streaming data, etc.
Capabilities

How the capabilities work together

The distinction isn’t any single feature. It’s how these capabilities work together without tight coupling to one database, one agent framework, one LLM, or one proprietary ecosystem.

CapabilityVOICE approachEnterprise benefit
Data accessFederated, standards-based access across existing Data SpacesLess migration and duplication
Semantic contextRDF, Linked Data, ontologies, and semantic data virtualizationConsistent entity identification and relationship discovery
Agent orchestrationLoosely coupled Agents, Skills, Tools, and Data SpacesFreedom to change agent frameworks and tools
LLM selectionCost-based routing across supported modelsGreater flexibility and cost control
Identity and governanceVerifiable identity (YouID) and fine-grained ABACGoverned access for humans and agents
Persistent memoryRDF-based session history, relationships, and provenanceReusable knowledge across interactions
Execution tracesMachine-computable records of relevant agent activities and outcomesAuditability, debugging, and reproducibility
Progressive enrichmentNew findings and relationships incorporated into persistent contextKnowledge that accumulates rather than disappearing between sessions
A concrete example

Enterprise contract intelligence

“Which customer contracts are affected by a supplier’s new compliance requirements, and what actions should we take?”

01 — Discover
Find what is relevant
Identify relevant contracts, suppliers, customers, and compliance requirements across databases, document repositories, and APIs.
02 — Connect
Correlate across sources
Use shared identifiers, RDF relationships, and ontologies to correlate information across those sources.
03 — Recall
Start from what is already known
Retrieve relevant findings, decisions, and execution traces from previous agent sessions.
04 — Reason
Pick the right model
Use an appropriate LLM alongside machine-computable context to evaluate potential impacts.
05 — Act
Governed actions only
Invoke authorized tools to prepare reports, create tasks, or initiate approval workflows, subject to access controls.
06 — Enrich
Keep what was learned
Preserve useful findings, new relationships, provenance, and execution outcomes for future interactions.

The next agent session doesn’t have to rediscover everything from scratch. Knowledge accumulates. Context improves. Actions remain governed.

How VOICE differs

An architectural choice, not a replacement

VOICE complements the data, analytics, graph, and AI platforms an enterprise already runs, as well as offering an alternative to tightly integrated AI context stacks. Rather than making a particular platform the center of enterprise AI, it emphasizes six kinds of independence.

01
Data Space independence
Existing systems remain the authoritative sources.
02
Agent independence
Different agents and harnesses can use the same governed context.
03
LLM independence
Models can be selected or replaced according to task requirements and cost.
04
Standards-based interoperability
RDF, Linked Data, SQL, SPARQL, HTTP, ODBC, JDBC, MCP, and OpenAPI provide reusable integration interfaces.
05
Persistent, portable context
Machine-computable memory, provenance, and execution traces are not tied to one LLM’s conversation history.
06
Governance across boundaries
Identity, authentication, authorization, and storage remain distinct architectural concerns.
Business value

What VOICE is designed to do for an enterprise

  • Reduce integration costs by reusing existing systems and open standards.
  • Reduce AI operating costs through selective LLM routing and reusable context.
  • Reduce repeated work by preserving relevant session histories, execution traces, and accumulated knowledge.
  • Improve agent effectiveness by combining current enterprise information with progressively enriched semantic context.
  • Strengthen governance through fine-grained control over data access, memory retrieval, and action execution.
  • Protect existing investments by avoiding unnecessary migrations and platform dependencies.

Most AI platforms help agents work with data. VOICE is designed to help agents work across Data Spaces, remember what they’ve learned, and execute governed actions using that knowledge.

From intent to governed action

Context that grows more valuable over time.