Incomplete reads and honest outcomes
Do not turn a partial scan into a complete integrity result.
Research note · November 14, 2026Research question
What result should be shown when a file disappears or becomes unreadable during a check?
Method
- Use a controlled folder with a readable file, a permission-denied file and a file removed during scanning. Record successful reads and failures at the individual path level.
- Define completion separately from mismatch. A check can detect a changed file and still be incomplete because another file could not be read. Preserve both facts.
- Compare expected lengths with observed reads where the format provides that information. Retry only under a documented policy, and retain the first failure rather than quietly replacing the history with a successful retry.
Records to retain
- Attempted paths
- Read error and attempt time
- Bytes read and expected lengths
- Completion state and retry history
Source basis
OCI descriptors explicitly represent content size and digest. The useful lesson for a file-checking protocol is that receiving some bytes is not evidence that the intended object was read completely.
Interpretation & limits
A successful retry can observe a different filesystem state. This protocol does not claim an atomic filesystem snapshot or establish how Prompto handles every operating-system error.
Next experiments
- Inject read interruptions into a non-production fixture.
- Review whether incomplete checks can be mistaken for clean results.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.