Domo Parity And Backend Takeover¶
The goal is not to remove Domo from every workflow. The goal is to remove Domo as the hidden owner of backend logic.
LeafEnterprise should own deterministic backend processes. Domo can remain a presentation layer for live business deliverables and accounts when it consumes backend-published outputs.
Parity Matrix¶
| Capability | Legacy Domo posture | LeafEnterprise takeover posture | Why this is better |
|---|---|---|---|
| Scope selection | Card/page filters can obscure exact PBM/TPA/group/date lineage. | Scope is resolved by backend APIs and carried through report, AI, workbook, PDF, and dashboard outputs. | Prevents cross-scope leakage and makes runs reproducible. |
| Savings math | Beast Modes and DataFlows can encode opaque or duplicated logic. | Versioned Python/SQL formulas with tests and machine-readable calculation registry. | Formulas are inspectable, testable, and owned. |
| Claims rows | Dashboard extracts may hide source predicates. | AWS SQL and curated stores are queried through explicit backend filters. | Source rows can be replayed and audited. |
| Contract evidence | Pricing rows can appear authoritative without packet proof. | Exact Graph/OneDrive contract packets or governed pricing lineage required. | Final guarantee claims cannot be made from candidate evidence. |
| Rebate evidence | Dashboard lift assumptions can look final. | Rebate-backed claims require exact governed rebate evidence or remain blocked/modeled. | Avoids unsupported savings claims. |
| Request lineage | Work can be separated from Salesforce ITR intent. | Salesforce ITR mirror, evidence bundles, run plans, and queue handoff preserve request lineage. | Operators can trace the business ask to final output. |
| Artifact production | Dashboard state may not match workbook/PDF exports. | API, dashboard payload, workbook, PDF, and AI optimization share one backend context. | Client deliverables stay aligned. |
| Migration validation | Useful historical behavior but not runtime truth. | Domo exports become golden comparison packets and negative tests. | Legacy behavior is preserved without keeping hidden dependencies. |
| Agent automation | Not a governed execution plane. | Agents run through task ledger, policy gates, Service Bus, AKS workers, traces, and artifacts. | Automation is auditable and controllable. |
Takeover States¶
| State | Meaning | Domo role | LeafEnterprise role |
|---|---|---|---|
legacy_reference |
Domo documents how the process used to behave. | Historical comparison. | Build parity tests and replacement contracts. |
candidate_evidence |
Domo helps identify a row, formula, or business case. | Discovery input. | Require governed source proof before final use. |
golden_comparison |
Domo output is used to compare migration behavior. | Validation fixture. | Explain and approve differences. |
presentation_consumer |
Domo displays LeafEnterprise-published output. | Dashboard surface. | Source of scoped payload and readiness state. |
retired_backend_dependency |
Domo no longer decides backend truth. | Optional presentation/reconciliation. | Runtime authority. |
Required Proof Before Replacing A Domo-Backed Process¶
LeafEnterprise should not claim takeover until these are documented:
- source system and data table/object/file lineage;
- exact scope fields and allowed ambiguity states;
- formula implementation and test coverage;
- evidence sufficiency rule;
- output parity target;
- dashboard-publish contract;
- validation packet or golden comparison;
- owner and remediation path.
Presentation Contract¶
Domo-facing dashboards should receive one of these from LeafEnterprise:
- scoped API extracts,
- scheduled curated exports,
- workbook/PDF artifacts,
- dashboard-safe summary tables,
- machine-readable readiness and blocked-state fields.
They should not receive raw source credentials, raw PHI beyond approved minimum necessary extracts, Graph download URLs, Salesforce body URLs, or backend-only queue/tool secrets.
For the detailed Domo PDP, private embed, App Studio, and dual-enforcement model, use Domo Integration.