AI Executive Office — CXO Assistant Platform (On-Premises) · View 02 of 30 · 1 · Context and scope
The load-bearing decision
- The language model sits in the orchestration stage and nowhere else. It never appears in the data stage, and it holds no credential for any store — everything it learns arrives through the tool plane, carrying the caller's identity
- Reads fan out widely; writes converge on a single execution plane. That asymmetry is the whole governance model, and it is why the right-hand column has one solid arrow into it and many dotted ones out
- The tool plane is a set of first-party Model Context Protocol servers. MCP is the wire contract between the model and every read; it is not a new capability, it is the standardisation of the one that was always there
Deliberate omissions
- Guardrails, evaluation and audit are on every path but drawn only once, in view 29. Repeating them here would triple the arrows and say nothing new
- The detection pipeline that produces the morning brief runs beside this flow rather than inside it — view 18
Numbers
- Simple KPI question: p95 under 5 seconds, two model calls
- Cross-system investigation: asynchronous, 30–180 seconds, progressively disclosed rather than made to wait
- Morning brief: generated by 06:30 local, delivered 07:10
