The situation
A platform infrastructure incident exposed a difference between the live database history and the current application schema. Some functions could work in a fresh environment while historical Rooms remained vulnerable during container recreation.
The evidence-led response
The team preserved the canonical database, verified hashes and backups, traced the schema chain, and tested recovery against the real historical record rather than a clean substitute.
The result
Memory, Room entry and the governed reasoning chain were restored and tested. Durable storage and recovery behaviour were then verified before further design work continued.
Why it mattered
Continuity is not proved by a fresh demonstration. It is proved when the real record survives change and can be recovered without silent loss.
Important: Case notes are anonymised and limited to the records and purpose described. They are not promises of the same outcome in another matter.