Public evidence summary
Historical checkpoint-timeout correction
- Record date
- 8 September 2026
- Scope
- Historical evidence; the scope and environment are described in the recorded result.
- Current deployment
- Not independently verified by this historical evidence. Current availability
Recorded result
The 8 September 2026 record reports a correction for checkpoints that exceeded the previous fixed deadline. Tests verified an adjusted time allowance, bounded recovery after a timeout and explicit recording of failed checkpoints. The page reports deployment verification before the later soak resumed. Measurements came from one host and one storage class; the calibration did not track storage that degraded while the service was running. A prematurely started soak on the previous build was stopped, so it is not evidence for the corrected build.
The public summary as JSON. These are the same reviewed fields shown in Read.
{
"schemaVersion": 1,
"publicSummaryVersion": "2026-09-30",
"classification": "PUBLIC",
"title": "Historical checkpoint-timeout correction",
"summary": "The 8 September 2026 record reports a correction for checkpoints that exceeded the previous fixed deadline. Tests verified an adjusted time allowance, bounded recovery after a timeout and explicit recording of failed checkpoints. The page reports deployment verification before the later soak resumed. Measurements came from one host and one storage class; the calibration did not track storage that degraded while the service was running. A prematurely started soak on the previous build was stopped, so it is not evidence for the corrected build.",
"date": "8 September 2026",
"scope": "Historical evidence; the scope and environment are described in the recorded result.",
"result": "The 8 September 2026 record reports a correction for checkpoints that exceeded the previous fixed deadline. Tests verified an adjusted time allowance, bounded recovery after a timeout and explicit recording of failed checkpoints. The page reports deployment verification before the later soak resumed. Measurements came from one host and one storage class; the calibration did not track storage that degraded while the service was running. A prematurely started soak on the previous build was stopped, so it is not evidence for the corrected build.",
"sections": [],
"currentDeployment": "Not independently verified by this historical evidence.",
"canonical": "/evidence/phase-b39"
}
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 897850d31ccec495eb30fd47f4dabd0d6a901c7c17e0af15210743bd0bf9c873