Problem
Historical and damaged system material can be mistaken for current authority during recovery.
Engineering Case Study
Recover the system without promoting the archive.
Engineering case study: Lazarus-style recovery separates historical evidence, schema conformance, runtime reconstruction and promotion gates.
Lazarus recovery and hardening
The dangerous move in recovery is treating historical or damaged material as current authority. Lazarus reconstructs source paths, schema state and runtime evidence separately, so recovered state is promoted only after explicit conformance and acceptance.
Method
Source paths, schema state and runtime evidence are reconstructed separately.
Result
Recovered state can be promoted only after explicit conformance and acceptance.
Boundary
Recovery evidence may explain lineage without automatically becoming live runtime truth.
Current Evidence
Source paths, schema conformance and runtime evidence are reconstructed independently.
Recovered state stays held until conformance and acceptance pass.
Schema freeze, gaps and promotion decisions are recorded as evidence.