Domo Takeover Boundary¶
Domo takeover data is migration and reconciliation evidence. It is not a LeafEnterprise runtime dependency and must not replace deterministic backend calculations.
The point of the takeover is ownership. Domo can show how the outsourced or legacy BI process behaved, but LeafEnterprise must own the backend contracts that create scoped dashboard payloads, savings/audit outputs, and final deliverables.
What Domo Can Provide¶
- Historical card behavior.
- Beast Mode formulas as edge-case fixtures.
- Recovered process assumptions.
- Candidate pricing rows.
- Golden comparison packets for migration validation.
What Domo Cannot Authorize¶
- Final contract guarantee conclusions.
- Runtime savings/audit calculations.
- Rebate-backed optimization claims without exact governed evidence.
- Silent substitution for missing contract packets.
Promotion Guardrails¶
LeafEnterprise/domo_takeover/jobs.py must keep partial or invalid source manifests out of Azure SQL curation loads. Complete manifests, load ids, dataset ids, and calculation flaw gates are required before promotion.
Takeover Data Plane¶
| Layer | Purpose | Runtime authority |
|---|---|---|
| Leaf IQ export | Captures Domo cards, datasets, Beast Modes, and DataFlows. | No. It is source evidence. |
| ADLS bronze | Preserves immutable Domo-derived source snapshots. | No. It is replay evidence. |
| ADLS silver | Normalizes extracted datasets and metadata. | No. It supports validation. |
| Azure SQL curated | Holds complete promoted datasets and golden comparison packets. | Only for migration/reconciliation unless explicitly promoted into backend contracts. |
| LeafEnterprise API | Produces scoped report/dashboard/deliverable payloads. | Yes. |
Dashboard Implication¶
A Domo-facing client dashboard should consume LeafEnterprise-owned outputs. It may use Domo as a visualization surface or comparison target, but production dashboard values should come from backend-scoped APIs and artifacts.
For client-facing Domo delivery, use the Domo-native PDP/group/App Studio model plus LeafEnterprise backend authorization. See Domo Integration.
C-Suite Trust Message¶
Domo is strongest when it is the approved presentation layer for business users and client account views. LeafEnterprise is stronger as the backend authority because it can prove:
- which source rows were used;
- which formulas produced the outputs;
- which contract, pricing, rebate, or Salesforce evidence supported the result;
- which evidence was missing or candidate-only;
- which queue, worker, trace, and artifact produced the deliverable;
- which dashboard output was published for presentation.
That distinction lets Leaf Health keep Domo's presentation value without leaving deterministic backend ownership in dashboard logic.
Operator Posture¶
Use the Domo evidence to preserve business cases and negative tests. Implement the LeafEnterprise replacement using Azure SQL/ADLS evidence, deterministic Python/SQL calculations, queue-backed runs, packetized evidence, and workbook artifacts.