Execute a reproducible exit test

The test does not ask whether exit appears possible. It verifies that an identified minimum service can be restored on a given target using authorised assets and within limits approved by the authority named in the mandate.

Production may remain untouched: the exercise uses a controlled source state and an isolated target. Any extrapolation to the full system is written as a limitation.

Six prerequisites prevent a preparation failure from being confused with an impossible exit.

• Inventory — assets and dependencies within scope are available
• Target — capable of receiving and executing the selected assets
• Rights — export, use, copy, transfer and erasure have been examined
• Criteria — thresholds and critical functions approved before execution
• Security — window, rollback and stop conditions are defined
• Authorities — source, target, security and decision owners are named

Every phase reuses register identifiers and emits a dated trace. Any phase not executed remains visible in the conclusion.

An export manifest is not enough. Volumes, hashes, schemas, metadata, time conventions and access rights are checked, then the data is actually read or queried on the target.

An exclusion may be legitimate. It must still be exhaustive, justified, linked to its effect on the service and accepted before the conclusion is signed.

The target is rebuilt from versioned artefacts. Interfaces, identities, observability, backups and incident procedures are replayed. Secrets are recreated on the target, never copied in clear text.

Functional equivalence is not technical identity. Shared features and acceptable deviation between source and target are defined before comparison.

The stopwatch is only one measure. The file also records data loss, manual work and residual calls to the source.

• Coverage — critical assets present or exclusion accepted
• Integrity — no unexplained critical discrepancy
• Journeys — selected functions meet the prior threshold
• Recovery — duration and data loss within approved objectives
• Autonomy — critical operations executed without unplanned help
• Erasure — source inaccessibility shown under the applicable framework

The lead suspends the exercise if production data could be altered, a secret leaves controlled custody, return to the safe state becomes impossible or a newly discovered dependency falls outside the authorised scope.

Every stop retains the time, observed fact, consulted authority and resumption condition. Rollback is executed or its impossibility appears as a reservation.

The conclusion distinguishes demonstrated, conditional and unproven exit. It identifies unexecuted phases, gaps, residual dependencies, owners and the reassessment date.