Provenance Ops
Core Infrastructure

The Operating
Graph

A static SOP binder is useless the day it is printed. We build a dynamic, structured map of how your business actually functions—capturing the tribal knowledge that walks out the door when key employees leave.

The Problem

From "Tribal Rules" to Structured Data

When a business relies on unwritten rules—such as who gets called when a specific truck breaks down, or which customer situations always require escalation—it creates massive transition risk.

The Operating Graph structures the messy reality of your acquired business into an ontology that our Operator Command Layer can understand, monitor, and act upon.

Before: Tribal Knowledge

"When the Miller account calls, always transfer to Sarah—she knows their history."

"If it's after 3pm and the part isn't in stock, call Mike's cell, not the main line."

"The Johnson job is complicated—check the pink sticky on the monitor."

After: Operating Graph
Customer: Miller Corp → VIP Flag: True
Escalation Path: Account Manager → Regional Lead
After-Hours Protocol: SMS Primary, Call Secondary
Job: Johnson-2024-0847 → Full History Linked
Components

What the Graph Contains

Customer Lifecycle

From untracked intake forms to final cash collection—every touchpoint mapped.

Vendor Workflows

Supplier approval chains, payment terms, and escalation paths documented.

Exception Patterns

What goes wrong, how it is detected, and who decides the fix.

Staff Dependencies

Single points of failure, cross-training status, and knowledge concentration.

Reconciliation Routines

Shadow ledgers traced back to systems of record with variance explanations.

System Integrations

API connections, manual handoffs, and data entry bottlenecks identified.

Real Example

How It Works in Practice

Sample Graph Excerpt

Field Services Dispatch Workflow

Trigger Node
Service Request Received
  • • Source: Phone / Web / Email
  • • Timestamp: Auto-captured
  • • SLA Clock: Starts
Decision Gate
Triage Classification
  • • Emergency: < 4 hours
  • • Standard: 24-48 hours
  • • Scheduled: Customer choice
Action Output
Dispatch Assignment
  • • Tech match: Skills + Location
  • • Customer notified: Auto-SMS
  • • Route optimized: Real-time
Captured Rules:"If customer is flagged VIP and request is after 5pm, escalate to on-call manager before dispatch."
Scalability

The Path to Portfolio Command

The Operating Graph is the foundation for scalable ownership. For sponsors with multiple assets, establishing this structured data model enables a direct transition into Portfolio Command functionality.

Once the tribal rules are captured across your holdings, you can view standardized weekly operating briefs and exception rollups across multiple acquired businesses from a single, unified interface.

Single Asset vs. Portfolio

1
Single Asset Command

Weekly brief for one business with full operational visibility

2
Standardization Layer

Common metrics and exception types across all holdings

3
Portfolio Rollup

Cross-asset brief showing the top 5 issues across all companies

Build Your Operating Graph

The 30-day sprint captures your tribal knowledge and builds the first version of your Operating Graph.

Start the Sprint