interaction · version 2026.1
Cloud Governance Interaction Model
A bounded interaction flow from demand through specialist decisions into delivery and run.
Accessible diagram transcript
Objects
- Demand intake: Qualified need (Consumers)
- Governance: Route and coordinate (Governance)
- Specialist authority: Decision and conditions (Authorities)
- Service ownership: Service lifecycle (Service ownership)
- Platform delivery: Build and evidence (Engineering)
- Operations: Accept and operate (Operations)
Directed relationships
- demand → govern: request (handoff)
- govern → decide: refer (authority)
- govern → service: shape service (handoff)
- decide → deliver: conditions (authority)
- service → deliver: requirements (handoff)
- deliver → run: handover (handoff)
- run → govern: evidence (feedback)
When to use it
Use to clarify who acts, decides, hands over and accepts.
What to challenge
- Separate accountable authority from delivery execution.
- Make every important handoff directional and reviewable.
- Treat this reference pattern as a starting point, not a prescription.
Adapt it responsibly
- Rename functions to match the organization vocabulary.
- Remove elements that are genuinely out of scope.
- Validate decision rights and handoffs with accountable stakeholders.
Model contents
6 objects and 7 directed relationships. Every object keeps a stable semantic ID.
One model, multiple representations
The browser view and editable file are generated from the same canonical graph, so labels, roles and relationship direction stay aligned.
Clear visual grammar
Shape, color and connector style distinguish actors, governance, authorities, services, engineering, operations and providers.