Recovered Estate Evidence¶
The current recovered Domo estate already shows signs of the intended Domo-native entitlement pattern.
Source: C:\Users\LoganKronforst\Dev\leaf-iq\docs\catalog\client-dashboard-takeover-map.md.
High-Signal Client Dashboard Datasets¶
| Dataset | Rows | Columns | PDP | Cards | Interpretation |
|---|---|---|---|---|---|
Client Data for Reporting - Production |
15,536,561 | 137 | enabled | 89 | High-signal client dashboard dataset with Domo-native entitlement. |
Client Data for Reporting |
15,512,453 | 138 | enabled | 162 | High-signal client dashboard dataset with Domo-native entitlement. |
Golden Leaf Master Claims |
5,837,496 | 74 | enabled | 0 | Claims dataset with PDP enabled; likely useful for backend parity and Domo presentation scoping review. |
Takeover Implication¶
This evidence supports a dual strategy:
- preserve Domo PDP for Domo-native presentation and client-facing cards;
- move deterministic calculations, evidence sufficiency, generated artifacts, and API outputs into LeafEnterprise;
- validate that any Domo-facing replacement dataset includes entitlement columns needed for PDP;
- test each customer/account group as an access scenario, not just a visual filter scenario.
Open Validation Items¶
- Export or inspect PDP policies for the high-signal datasets.
- Map Domo groups to LeafEnterprise account, group, contract, and reporting-period scopes.
- Confirm App Studio/page/card sharing follows the same group model as PDP.
- Confirm no dashboard relies on dropdown filters as its only client isolation control.
- Build golden comparisons for key cards before replacing card-side formulas with backend-published metrics.