Shared responsibility

Infrastructure ownership changes who operates each layer.

The product should make those boundaries visible before a workload is placed.

Responsibility matrix

Responsibility	MIOSA-managed	OpenComputers	Bring Your Own Cloud
Control-plane service	MIOSA	MIOSA	MIOSA
Physical or cloud account	MIOSA	Customer	Customer
Host operating system	MIOSA	Customer	Shared through certified image and customer account
Host capacity	MIOSA	Customer	Customer provider resources, MIOSA desired state
Network perimeter	MIOSA	Customer host network	Customer VPC or subnetwork
Runtime generation	MIOSA	Customer-approved agent update	MIOSA-signed generation, customer-reviewed installation
Workload placement	MIOSA policy	MIOSA policy within connected hosts	MIOSA policy within enabled customer pools
Provider billing	MIOSA	Customer hardware and network	Customer cloud bill
Application data	Application owner	Application owner	Application owner
Drain and workload proof	MIOSA	MIOSA plus host availability	MIOSA plus provider observation

MIOSA responsibilities

• Maintain desired state and placement policy.
• Issue scoped, retry-safe operations.
• Verify immutable runtime generations.
• Record host acceptance evidence.
• Require fresh host sessions before placement.
• Reconcile provider and runtime drift.
• Drain workloads before an authorized teardown.
• Report health, capacity, usage, and next actions.

Customer responsibilities

• Choose the infrastructure ownership model.
• Review cloud IAM, network, and infrastructure packages.
• Maintain cloud quotas, billing, and organization policy.
• Protect Terraform state and provisioning identities.
• Select data stores, retention, backup, and recovery policy.
• Approve placement into a customer-cloud region.
• Revoke access when the trust relationship should end.
• Coordinate destructive cloud changes with MIOSA drain state.

Cloud-provider responsibilities

• Operate the underlying cloud services.
• Enforce the configured provider identity and network policy.
• Report provider state and billing.
• Provide the compute, storage, and network primitives requested by the customer.

Safe change order

sequenceDiagram
  participant Customer
  participant MIOSA
  participant Provider
  participant Host

  Customer->>MIOSA: request infrastructure change
  MIOSA->>Host: stop new placement and drain
  Host-->>MIOSA: zero-runtime evidence
  MIOSA-->>Customer: safe provider change authorized
  Customer->>Provider: apply reviewed change
  Provider-->>MIOSA: provider observation
  Host->>MIOSA: fresh acceptance and heartbeat
  MIOSA-->>Customer: placement may be enabled

Do not terminate a host because its time-to-live expired or its provider record looks stale.

Termination requires exact ownership plus fresh drain, zero-runtime, and session-revocation evidence.

Provider healthy is not MIOSA ready

A running VM is not sufficient. The runtime, storage, authenticated session, guest boot, capability advertisement, and placement scope must also agree.

Customer infrastructure overview Compare MIOSA-managed compute, OpenComputers, and customer-cloud regions.