Continuity built in.
Not bolted on.
Disaster recovery usually runs as a separate project, with its own tools, its own runbooks and its own third-party site. On Oasis Stack it is part of the platform your teams already operate, sized to each workload.
DR is usually a second platform nobody runs until the worst day.
It lives outside the primary estate, with its own tooling and its own dependency on a third-party site, so it is tested least when it matters most. Continuity should be a property of the platform, not a separate programme.
Where a workload can recover to.
Recovery targets are set per workload: another site of your own, a partner Oasis cloud by agreement, or a public cloud for the non-sensitive workloads you select. The DR site can be a full deployment, or Oasis Edge Cloud: a mini deployment for just the critical workloads.
Recovery targets per application, not per platform.
The runbook is the platform.
Data goes where you place it, and nowhere else.
Recovery moves data by design, so the rules about where it may go are written down in advance.
Make continuity part of the platform.
Start with your workloads and the recovery each one needs.