Operational AI infrastructure · early access 2026

The operational graph for your organization. Build it visually. Agents act on it.

Connect every operational system — GitHub, CRM, ERP, sensors, EHR. Drag rules onto a canvas. Predicates fire on meaningful state changes. Agent workflows respond, with full causation lineage from signal to action.

5 layers
operational substrate
signals
connector framework
Full lineage
audit-grade by default
SOURCESONTOLOGYWORKFLOWSGitHubSalesforceSAPSlackStripeEHR · FHIRSensorsHubspotCustomPREDICATE TRIGGERmatch: lead.score > 80Spec pipelineCode reviewLead routingIncidentCompliancePatient flowYour workflowSAME PLATFORM · ANY INDUSTRY
Any signal
MES · SCADA
SAP S/4HANA
ORACLE NETSUITE
SALESFORCE
WMS · TMS
HUBSPOT
SLACK · TEAMS
SENSORS · MQTT
OPC-UA
EHR · HL7 / FHIR
JIRA · LINEAR
GITHUB · GITLAB
DATADOG · NEW RELIC
STRIPE
CUSTOM WEBHOOKS
MES · SCADA
SAP S/4HANA
ORACLE NETSUITE
SALESFORCE
WMS · TMS
HUBSPOT
SLACK · TEAMS
SENSORS · MQTT
OPC-UA
EHR · HL7 / FHIR
JIRA · LINEAR
GITHUB · GITLAB
DATADOG · NEW RELIC
STRIPE
CUSTOM WEBHOOKS
Thesis

Organizations are becoming too complex for human-only coordination. The systems that should resolve this — CRM, ERP, ticketing, comms, sensors — instead create more fragmentation than they unify. The operational layer is the missing infrastructure of AI-native enterprises.

Architecture

Five layers between raw signal and coordinated response.

Each layer is inspectable, replayable, and self-hostable. Time-travel through any state. Replay any trigger. Audit any action. Designed for environments that cannot afford black boxes.

01
Ingestion
webhook-gateway
HMAC-verified webhooks from any source normalize into a unified domain event shape. Attribute and relation diffs computed at the edge. Idempotent dedup by source key.
HMAC · DEDUP
~200 SOURCES
02
Ontology
event-core
Current state of every entity, relations as first-class citizens, soft-delete for time-travel. Tenant-isolated. Projection rebuilds idempotently from the event log.
POSTGRES · REDIS
EVENT-SOURCED
03
Predicates
trigger-engine
Workspace-scoped rules expressed as AST. Extensible library of L2 functions. Predicate simulation against historical data — test before you trigger anything live.
AST · L2 LIB
SIMULATABLE
04
Causation
audit-log
Every chain — raw event → derived event → trigger fired → workflow run → action taken — recorded with full lineage. Compliance-ready out of the box.
HIPAA · SOC 2
QUERYABLE
05
Agents
workflow-runner
Workflow templates as ordered sequences of role × agent. Anthropic Managed Agents under the hood. Provider-agnostic SDK for OpenAI, Gemini, or local models.
ANTHROPIC · OPENAI
SELF-HOSTABLE
Visual builder

Compose predicates that span systems. No code required.

Every signal — from MES, IoT, ERP, CRM, ticketing — becomes a draggable source. Compose rules that fire only when signals align across systems. Actions chain off triggers, with full lineage from raw signal to outcome. Single-system tools structurally can't do this.

workspace · automations · equipment-failure-prediction
mes:vibration.anomaly
event source
iot:bearing.temperature
event source
erp:maintenance.window
event source
Bearing failure predicted in < 4 hours
active
equipment.failure.predicted
rule
action
Message
preview

Halt line {lineId}: schedule hot-swap before failure window

Message
preview

Page maintenance lead: pre-cut work-order #{wo} attached

Drag & dropAuto-layout (dagre)Predicate simulationReplay against historyOne-click rollback
Use cases

Four operational domains. One canvas.

Same five layers, same predicate engine, same agent runtime. Only the source schemas and workflow templates change. Each domain inherits causation lineage and audit-grade governance by construction.

01
Manufacturing operations

Line-down events, coordinated across MES, ERP, and shift teams

mes:machine.alert
event source
predicate
severity ≥ critical & station.criticality = high
Pause upstream line
Project quality impact
Escalate to shift supervisor

Sensor telemetry, MES context, and human response unified in one causation graph. From signal to action — fully traced.

02
Logistics & supply chain

Cross-system response to delayed shipments

wms:shipment.exception
event source
predicate
eta_delta > 12h & customer.tier ∈ {enterprise, strategic}
Carrier rebooking
Customer comms draft
Finance impact projection

WMS, TMS, ERP, and customer systems coordinate one response. Lineage from carrier event to customer message — audit-ready by default.

03
Enterprise workflows

Fragmented context, unified for governance

any:entity.modified
event source
predicate
governance.tier = controlled & crosses_boundary = true
Aggregate context
Evaluate policy
Route to reviewer

Every cross-system change surfaces with its full operational context. No reconstruction from log files, no orphaned audit trails.

04
AI command centers

Human + AI coordination, with full lineage

agent:workflow.completed
event source
predicate
confidence < 0.85 OR financial_impact > $100k
Reasoning summary
Counterfactual projection
Operator approval queue

AI proposes; humans confirm. Every autonomous decision recorded with its causation chain — explainable, auditable, governed.

Causation log

Every action carries its causation chain.

Lineage is a structural property of the substrate, not a feature added on. Compliance, debuggability, and governance become byproducts of the architecture — from raw signal through predicate, workflow, and outcome.

workflow run · wf_01H8KQ7N3F4M2P · live trace
14:23:01.044
RAW
SOURCE EVENT · github.pull_request.opened
repo: "acme/platform" · pr: #1284 · files: [migrations/0042_add_index.sql, …]
payload size: 12.3kb · ingest: webhook-gateway · idempotency: ✓
14:23:01.067
EVT
DOMAIN EVENT · entity.pull_request.created
attrs: { author, base, head, file_count, has_migration: true }
projection updated · 4 relations created · caused_by: RAW above
14:23:01.072
TRG
PREDICATE MATCH · db-migration-review
match: files contains "migrations/" → true
L2 fn: contains_path · evaluated in 4ms · 1 trigger fired
14:23:01.081
WF
WORKFLOW START · db-migration-review/v3.2
steps: [schema-checker, backwards-compat, reviewer-suggestion]
runner: anthropic · model: claude-opus-4-7 · run_id: wf_01H8KQ7N3F4M2P
14:23:14.402
ACT
ACTION TAKEN · github.pr_comment.posted
target: acme/platform#1284 · caused_by: wf_01H8KQ7N3F4M2P
audit row written · time-to-action: 13.4s · explainable in one click
Why now

Three structural shifts converging in 2026.

→ 01

Managed agents reach GA.

Anthropic and OpenAI ship production-grade agent runtimes. The build-it-yourself moat is gone. Differentiation is the substrate agents coordinate over.

→ 02

Operational fragmentation is universal.

Modern enterprises run 50+ operational systems. Signals are abundant. What is missing is composition, causation, and coordinated response across system boundaries.

→ 03

Substrate is the missing layer.

Every vertical AI product reimplements the same five layers — usually under-specified, rarely audit-grade. Done right, the substrate is shared infrastructure, not duplicated work.

Critical infrastructure is built with serious partners.

Design partners shape the v1 architecture. Private workspace, weekly working sessions with the founding team, and direct input on the schema, predicate library, and workflow primitives.

Invite-only access·hello@zrg.dev