Your obligations,
before they're
breached.

Intelipi models your operations as a living system, tracks every time-bound commitment in flight, and alerts your ops team when one is at risk — with the math, the rule, and the recommended action.

REASONING PRIMITIVES
04 TYPES
FIRST VERTICAL
2026 · FREIGHT
TYPICAL POC
02 WEEKS
↳ LIVE REASONING TRAIL FX-8821
AGENTDemurrageWatch
AT RISK
Shipment #FX-8821 at risk — projected demurrage $8,240 over 14 days free time.
STEP 01·DETERMINISTIC
Free time: 7 days · per Master BL clause 4.2
STEP 02·RULE
Carrier tariff: $120/day demurrage over free time · HMM-TARIFF-2025-Q2
STEP 03·EMPIRICAL
Historical dwell at this port: 18.3 days avg · n=412 · σ=4.1 · 24-mo window
STEP 04·LLM JUDGMENT
Severity: HIGH · confidence 0.86 · model-check passed
OBLIGATIONS BEFORE BREACHTYPED REASONING TRAILSPRIMITIVES vs ARTIFACTSTUNABLE POLICIESHUMAN IN THE LOOPRULES · BASELINES · SCENARIOSDOCUMENTS AS INPUTSONE PLATFORM · MULTIPLE VERTICALSOBLIGATIONS BEFORE BREACHTYPED REASONING TRAILSPRIMITIVES vs ARTIFACTSTUNABLE POLICIESHUMAN IN THE LOOPRULES · BASELINES · SCENARIOSDOCUMENTS AS INPUTSONE PLATFORM · MULTIPLE VERTICALS
§ 01 · THE PROBLEM
Operational teams don't fail because they lack data. They fail because obligations are scattered across contracts, systems, and the heads of senior operators — and nobody sees the breach coming until it happens.
§ 02 · THE PLATFORM

Three things
nobody else does
together.

01 ·

A living model of your operations

Shipments, obligations, events, and contracts — modeled as one navigable picture your team and our agents reason from.

  • One ontology across every domain
  • Documents feed the model — not the other way around
  • Primitives stay separated from artifacts
02 ·

Agents that show their work

Every conclusion carries a typed reasoning trail. Deterministic math, contract rules, empirical patterns, and LLM judgment — labeled step by step, never blended.

  • Four reasoning types, explicitly labeled
  • Inputs · method · confidence at every step
  • Provenance back to the source document
03 ·

Tunable, auditable, yours

Your ops team sets thresholds, tolerances, and escalation rules directly in the UI. Agents declare which policies they consult. Full versioned audit history.

  • No engineering tickets to change a threshold
  • Decision log per finding — seen, actioned, dismissed
  • Built for regulated industries from day one
§ 03 · DEEP DIVE

Every trail
declares its
reasoning.

Most AI products hand you an answer. We hand you the answer plus the four kinds of thinking that produced it — kept strictly distinct, labeled in the trail, auditable in the UI.

DETERMINISTIC

The math

Joins, lookups, arithmetic. Fully auditable, no estimation. When a trail step is deterministic, the answer is the only possible answer given the inputs.

reliability: exact
RULE

The clause

An extracted contractual or regulatory rule applied to live data. Every rule step links back to the source document, the page, and the clause — and the extraction version that produced it.

reliability: extraction-quality bound
EMPIRICAL

What usually happens

Statistical inference from your own history. Steps report sample size, confidence, and the window the pattern was computed over. Never confused with the rule.

reliability: stated with confidence interval
LLM JUDGMENT

Where language lives

Semantic interpretation, severity classification, recommendation drafting. Every judgment step declares a confidence score, the model used, and whether a deterministic sanity check passed.

reliability: bounded, labeled, checked
↳ EXAMPLE TRAIL · HEALTHCAREPT-44021
AGENTAuthorizationGuard
AT RISK
Patient PT-44021 pre-auth will lapse 34h before scheduled procedure OR-3.
STEP 01·DETERMINISTIC
Pre-auth window: 72h · per Aetna PPO policy §7.1
STEP 02·RULE
CPT 27447 requires clinical review + orthopedist sign-off · payer-rule AETNA-OR-2024
STEP 03·EMPIRICAL
Median reauth turnaround this payer: 41h · n=187 · last 90 days
STEP 04·LLM JUDGMENT
Severity: HIGH · revenue exposure $18,400 · confidence 0.91
↳ Every step is queryable. Every step has provenance. Nothing blends the four kinds of thinking.
§ 04 · BUILT FOR

Mid-size operators
managing millions
in obligations.

Not Fortune 500. Not SMB. The underserved middle — where the obligations are complex, the margins are thin.
ROLLOUT FREIGHT & SHIPPING · LAUNCHING 2026 HEALTHCARE, HOSPITALITY, FIELD SERVICE · 2027
Launching 2026
01 /

Freight & Shipping

Ports, tariffs, booking desks
OBLIGATIONS TRACKED
Free timeDemurrageDetentionBooking cutoffAMS/ACI filingsCustoms windows
2027
02 /

Healthcare

Hospital systems & ASCs
OBLIGATIONS TRACKED
Pre-authorizationMedical necessityFiling deadlinesReadmission windowsOR utilization
2027
03 /

Hospitality

Hotel & resort groups
OBLIGATIONS TRACKED
Group cutoffAttritionComp nightsEvent holdsOTA rate parity
2027
04 /

Field Service

Asset-heavy service ops
OBLIGATIONS TRACKED
Response SLAPM windowsParts ETAWarrantyCompliance inspections
§ 05 · NEXT STEP

Scope a PoC
on your data.

Tell us about one obligation type that's costing your ops team. We'll scope a focused proof-of-concept against a sample of your world — real contracts, real events, real trails — so you can see how the four reasoning types behave when the finding is yours.

Scoped to one obligation type you choose.
Built against a sample of your data, not a generic demo.
Weekly read-out with your ops lead until we agree it works.
REQUEST POCINTELIPI / 01.F