AI Executive Office — CXO Assistant Platform · View 09 of 30 · 3 · Structure
Decisions
- Read integrations are pulled on a declared cadence rather than pushed. A source that pushes is welcome to, but the platform never depends on it, because a missing push is invisible and a missing pull is an alert
- The existing lake is mounted as a OneLake shortcut rather than copied. Copying a customer's warehouse into the platform doubles the storage bill and creates a second version of the truth
- Writes exist on exactly two interfaces. Every other arrow out is a notification
Numbers
- Fourteen interfaces at go-live; the prototype takes three (ERP/finance, procurement, projects)
- Cadences: seconds (events), 15 minutes (finance CDC), hourly (projects), 4-hourly (documents), nightly (HR, CRM, market)
- Each interface carries a freshness contract, and the answer states which one it used
Risks
- Legacy public-sector ERPs frequently have no CDC capability. The fallback is a nightly full extract, which changes what "what changed since yesterday?" can honestly mean — and the answer must say so
- The workflow engine write is the highest-blast-radius interface in the platform. It is the one with a dedicated connector identity and a re-check at execution time (view 20)