AI Executive Office — CXO Assistant Platform (On-Premises) · View 07 of 30 · 3 · Structure
The layering rule
- A layer may call the layer below it and nothing above. The single upward arrow — the execution plane reporting an outcome to the decision engine — is asynchronous and passes through a queue, so it is a message rather than a dependency
- Grounding is a layer of its own, between orchestration and the AI platform. Collapsing it into the orchestrator is the mistake that makes tool authorisation impossible to audit later
- The metric service is the only component permitted to compute a KPI. Every other path to a number is a defect, and a test enforces it
- The grounding layer speaks MCP upward to the agents and each source system’s own protocol downward. That is what keeps a new domain to a new server rather than a change in the orchestrator
Deliberate omissions
- The cross-cutting band is drawn as a layer because the generator stacks bands. It is not a bottom layer: identity, keys, policy and monitoring touch every layer above
- Individual specialist agents are one box. Ten capability packs share one runtime — view 16
Risks
- Eight layers is a lot of indirection for a first release. The mitigation is that the grounding and orchestration layers ship as one deployable in the prototype and separate only when a second consumer appears
