Recovery strategies
The answer to a scenario: what it declares, what it depends on, and what validation means.
What a strategy declares
A strategy answers a scenario and applies to one or more business processes. It declares the type of response — recover, transfer, accept, among others — and what has to exist for it to work.
Dependencies
A strategy can depend on a specific supplier or asset: an alternate site, a contingency contract, a replica system. Declaring that dependency is what lets the platform notice when the answer to a scenario rests on something that is itself at risk.
It is a question that only makes sense once suppliers and assets already live on the platform — the strategy points at the real record, not at a typed name.
Primary strategy
Among the strategies covering a process, one is primary: the one the organization actually intends to execute. The others are alternatives. The distinction matters in the coverage view, which assesses the primary — having three never-rehearsed alternatives is not the same as having one ready answer.
Validation
A strategy carries the date of its last validation — the most recent exercise or test that confirmed it works. A strategy never validated, or validated more than twelve months ago, shows as stale in coverage.
Strategies of the accept type are excluded from that count, and not by oversight: accepting is a decision, not a procedure to rehearse. Demanding a rehearsal of a decision would produce an open item nobody can close.