Re-sealing an account retires every old copy of its saved content

The public summary as JSON. These are the same reviewed fields shown in Read.

{
  "schemaVersion": 1,
  "publicSummaryVersion": "2026-09-30",
  "classification": "PUBLIC",
  "title": "Re-sealing an account retires every old copy of its saved content",
  "summary": "The re-seal record dated 10 October 2026 reports seven passing test assertions on the laboratory platform, with none left unproven. After an account was re-sealed under a new key, a session saved in the older format and one saved in the current format both resumed byte for byte, content sealed under the old key could no longer be read from the live store or a backup copy, and the formerly older-format session could then be deleted on its own. A re-seal interrupted partway left the session readable and completed when run again, a session under a preservation hold was refused untouched, and two deliberately broken controls each failed as they should.",
  "date": "10 October 2026",
  "scope": "Historical record; any production observation is limited to the dated test described below.",
  "result": "Seven of seven assertions passed and both broken controls were caught. Every session came back byte for byte under the new key, and content sealed under the old key was unreadable from every copy. One engine on the laboratory platform is covered; production deployment is outside this record.",
  "sections": [],
  "currentDeployment": "Not independently verified by this historical evidence.",
  "canonical": "/evidence/phase-er-1sm"
}

Download this public summary

This derivative has its own digest. It is not the original transcript or a new test. Historical original records are preserved privately.

Download public JSON →

SHA-256 0a013c609e89891d6bd06e3ebf1854908c619dc44199d2471299d523506a8b34