System Authority¶
LeafEnterprise is the owned backend system for Leaf Health's savings/audit, client-reporting, contract-evidence, agent-execution, and deliverable workflows.
The system is not a Domo dashboard clone and not a front-end-only portal. It is the backend authority that resolves scope, reads governed source data, performs deterministic calculations, blocks unsupported evidence claims, and produces client-facing payloads and artifacts.
For executive review, start with:
Authority Statement¶
LeafEnterprise owns the following decisions:
| Authority | Backend-owned decision |
|---|---|
| Scope | Which PBM, TPA/broker, group, date window, and source request define a run. |
| Calculation | Which source rows and formulas produce each metric. |
| Evidence | Which contract, pricing, rebate, Salesforce, workbook, and packet records can support a conclusion. |
| Queueability | Whether a request can run automatically, must be resolved by an operator, or is blocked. |
| Dashboard payload | Which scoped data is safe to expose to a frontend or Domo-facing dashboard. |
| Deliverable | Whether report, PDF, workbook, and AI optimization outputs are ready and aligned. |
| Agent action | Which MCP/API/tool actions are allowed, blocked, preview-only, or dispatched to AKS workers. |
Non-Authority Rules¶
These systems can contribute evidence, but they do not authorize final savings/audit conclusions:
| System | Role | Boundary |
|---|---|---|
| Domo | Migration evidence, reconciliation behavior, legacy formula discovery, frontend-consumption context. | Not runtime authority for savings, pricing, rebate, or contract guarantees. |
| AI model output | Explanation, summarization, drafting, operator assistance. | Not a calculation source and not evidence by itself. |
| Historical workbooks | Source evidence and renderer parity fixtures. | Not copied blindly when formulas, scope, or contract inputs are stale. |
| Raw share-drive paths | Discovery and packet intake. | Not exposed to browser payloads or agent tools without governed packetization. |
End-To-End Chain¶
flowchart LR
Request[Salesforce ITR / operator scope] --> Scope[Governed scope resolution]
Scope --> Sources[Claims, contracts, pricing, rebate, packet evidence]
Sources --> Calc[Deterministic savings/audit calculations]
Sources --> Evidence[Evidence sufficiency checks]
Calc --> Payload[Scoped dashboard/report payload]
Evidence --> Payload
Payload --> Deliverables[Workbook, PDF, narrative, optimization]
Payload --> Dashboard[Frontend and Domo-facing dashboard consumers]
Payload --> Agents[MCP tools and enterprise agents]Agent Retrieval Rule¶
Future enterprise agents should retrieve this section before calling APIs or provisioning MCP tools. Route references explain how to call the backend; this section explains when a call is authoritative, when evidence is insufficient, and which source system is allowed to support a client-facing claim.
Machine-readable companions: