AI Executive Office — CXO Assistant Platform · View 01 of 30 · 1 · Context and scope
Scope decisions
- In scope: the conversational front door, the orchestrator and specialist agents, the decision engine, the governed execution path, and the semantic and knowledge layers that ground every answer
- Out of scope: replacing any system of record, replacing the enterprise BI estate, and any autonomous write. The platform reads widely and writes narrowly, through one path, after a human approval
- Email and calendar are in the picture but behind a per-tenant switch. Several public-sector tenants will not permit it, and the architecture must be correct with the switch off
Assumptions
- 3–8 executives and 20–200 business-unit heads per tenant; the platform is sized for hundreds of concurrent users, not thousands of simultaneous questions
- Every source system has an API or a supported extract. Where it does not, a file drop on a schedule is accepted rather than a screen-scrape
- The customer already has Microsoft Entra ID, or federates to it. Identity is not something this platform invents
Risks
- The executive's real front door today is a person, not a screen. If the chief of staff is faster, the platform is shelfware regardless of its accuracy — view 04 is where this is fought
- Sixteen integrations is the programme risk. The 4-week prototype takes three (view 22 explains why the count, not the depth, is what kills the timeline)
