Approvals, Baselines & Drift

Engines propose, people approve

Every application, dependency, protection pairing and plan an engine finds arrives as a proposal in the Approval Center. Nothing enters a recovery plan or a baseline until someone with approval rights accepts it. A rejected proposal is recorded and is not proposed again.

Baselines

Approving an application's recovery model freezes it as a baseline: its structure and intent — components, dependencies, protection pairings, plan steps, required targets. Live readings such as replication lag are deliberately left out, because they change constantly and are not what was approved.

Drift

Drift is the difference between the active baseline and the current state, not between last week's scan and this one. That answers the question an auditor asks — has anything changed since the plan was approved? Drift is ranked by its consequence for recovery: one changed recovery target outranks ten renamed steps.

Access

DRM runs inside the same console and behind the same login as the rest of the platform. It is granted per organisation; organisations without it do not get access to DRM's pages or API. Approving and authoring are separate permissions from viewing.