{
  "format": "vercy-enterprise-profile-candidate/v1",
  "contourId": "EM-RSK-04",
  "name": "Enterprise Business Continuity and Recovery",
  "decision": "PROFILE",
  "newRuntimeId": false,
  "bases": [
    "WM-ACT-043"
  ],
  "constraints": [
    "Business Impact Analysis and Continuity Plan remain WM-ACT-043-owned immutable releases; BIA includes maximum tolerable disruption and maximum tolerable data loss.",
    "Reusable Restore Verification is a WM-ACT-043-owned specification distinct from Backup Policy, RestoreTest occurrence and RecoveryEvidence; only cross-domain reuse is deferred.",
    "Restore Verification owns executable criteria and cites a policy version whose scope is limited to cadence and minimum requirements.",
    "Observation outcomes are exactly verified, verified-with-limitations, failed, blocked-by-dependency, indeterminate-insufficient-observation and not-attempted; objective verdicts are separately attained, breached or not-evaluable.",
    "RTO/MTPD and RPO/tolerable-loss comparisons require identical subject, scope qualifier, degraded level and pinned BIA release.",
    "Recovery order is derived and owned by the ContinuityPlan release; every exercise and activation pins it and the WM-XCT-037 source-graph version.",
    "Isolation crossings, bootstrap assumptions and fixture representativeness have the binding outcome caps defined by the allocation invariants.",
    "Restore verification and RecoveryEvidence carry the complete time base, validity window and traceability pins before any recovery claim is publishable.",
    "Restoration, recovery, reconstitution and closure remain separate; an unmet required dependency blocks chain scope and refuses closure."
  ],
  "holds": [
    "WM-ACT-043 remains non-canonical and its composition and interoperability gaps block publication.",
    "WM-ACT-008 and WM-ACT-042 are unapproved; WM-XCT-037 and WM-SFT-016 are explicitly unverified for this profile.",
    "Backup / Data Protection Policy has no allocated identifier; no canonical or runtime publication is authorized."
  ],
  "candidateRevision": 3,
  "status": "provider-reconciled-audited-remediated-allocation-held",
  "canonicalPublishable": false,
  "constraintRules": [
    {
      "id": "RSK04-PROFILE-IDENTITY-001",
      "rule": "Reusable Restore Verification is a WM-ACT-043-owned specification distinct from Backup Policy, RestoreTest occurrence and RecoveryEvidence; only cross-domain reuse is deferred."
    },
    {
      "id": "RSK04-PROFILE-OUTCOME-001",
      "rule": "Observation outcomes are exactly verified, verified-with-limitations, failed, blocked-by-dependency, indeterminate-insufficient-observation and not-attempted; objective verdicts are separately attained, breached or not-evaluable."
    },
    {
      "id": "RSK04-PROFILE-COMPARE-001",
      "rule": "RTO/MTPD and RPO/tolerable-loss comparisons require identical subject, scope qualifier, degraded level and pinned BIA release."
    },
    {
      "id": "RSK04-PROFILE-ORDER-001",
      "rule": "Recovery order is derived and owned by the ContinuityPlan release; every exercise and activation pins it and the WM-XCT-037 source-graph version."
    },
    {
      "id": "RSK04-PROFILE-TRACE-001",
      "rule": "Restore verification and RecoveryEvidence carry the complete time base, validity window and traceability pins before any recovery claim is publishable."
    }
  ]
}