Skip to content

Executive Backend Trust Case

LeafEnterprise is the controlled backend system for deterministic PBM savings analysis, audit production, contract evidence, request intake, and agent execution. Domo can remain a business presentation layer where it is already approved for live account deliverables, but it should consume LeafEnterprise outputs rather than own the logic.

This division gives leadership the practical best of both systems:

Responsibility LeafEnterprise Domo
Calculation truth Owns formulas, SQL filters, evidence gates, run lineage, blocked states. Displays approved outputs.
Evidence ownership Owns contract packets, Salesforce evidence bundles, source manifests, ADLS artifacts. Can show linked summaries or published extracts.
Process automation Owns queues, workers, agent tasks, validation, replay, and artifact generation. Should not be the automation control plane.
Client-facing presentation Publishes scoped payloads and deliverables. Can remain the presentation/SOC/PHI-governed dashboard surface when vendor and client approvals cover that use.
Auditability Preserves reproducible inputs, formulas, traces, run ids, and artifact ids. Provides presentation history and reconciliation evidence.

Why LeafEnterprise Is Safer For Backend Ownership

LeafEnterprise is stronger than a dashboard-owned backend because it makes every material claim reproducible:

  • scope is resolved by backend contracts, not card filters;
  • source rows are tied to run id, PBM, TPA/broker, group, and date window;
  • formulas are implemented in versioned Python/SQL code;
  • contract, pricing, and rebate claims require governed evidence;
  • missing evidence becomes an explicit blocked state;
  • outputs can be replayed through API payloads, workbook exports, PDFs, traces, and artifacts;
  • agent actions are policy-gated and ledgered.

Why Domo Still Has A Role

Domo remains useful as a presentation and account-delivery layer when the current vendor/security posture supports that use. It can serve:

  • live business dashboards,
  • client account views,
  • executive presentation surfaces,
  • historical comparison views,
  • migration validation dashboards.

The boundary is that Domo should not silently own formulas, evidence sufficiency, contract guarantee conclusions, or rebate-backed savings claims. Those belong in LeafEnterprise.

Compliance Posture

These docs do not certify any vendor as compliant by themselves. The operating rule is:

  • use Domo for PHI/client presentation only where Leaf Health's vendor agreements, BAA/security review, and client permissions allow it;
  • use LeafEnterprise for deterministic backend processing, lineage, evidence controls, and source-system governance;
  • never expose raw Graph links, SQL credentials, Salesforce body URLs, ADLS paths, or backend secrets through Domo or browser payloads;
  • publish only scoped, approved, least-necessary dashboard outputs to presentation tools.

Leadership Decision Standard

LeafEnterprise should be trusted to take over a backend process when it can show:

Proof Required signal
Scope proof One exact governed scope or explicit blocked resolution.
Source proof Source system, table/file/object id, manifest, hash, or request id.
Calculation proof Named formula and implementation path.
Evidence proof Exact packet, candidate-only state, or blocked evidence reason.
Output proof Matching API payload, workbook/PDF/dashboard extract, and artifact lineage.
Operational proof Queue/worker trace, validation result, and rollback or remediation path.

If a process cannot meet this standard yet, it should remain marked as migration, candidate, modeled, or blocked rather than presented as final production truth.