A technical article had been revised locally, and the completion record contained the revised file's hash. The cloud copy provided for review still contained the earlier draft.
The URL had not changed. That did not establish which text it contained. Comparing the local revision and the review copy as separate artifacts revealed the mismatch.
A filename and a URL do not identify the revision
In the saved records from October 20, 2026, the revised local draft was 5,387 bytes. The review copy was 3,171 bytes. The revision added information about the verification scope, while the review copy retained the earlier explanation.
The entire review text matched the preserved old draft. The current local manuscript matched the SHA-256 recorded when the revision was completed.
Those checks established two different states: the local revision existed, and the delivered copy matched the old draft. An accessible URL and an unchanged filename did not distinguish them.
Separate the original, the intended snapshot, and the readback
For this UTF-8 Markdown workflow, three artifacts have different jobs:
| Artifact | Purpose |
|---|---|
| Working original | The document that can continue to change |
| Manuscript snapshot | The exact text intended for this handoff |
| Text read back from the review copy | An observation of what the destination contains |
After updating the review copy, the readback string was encoded as UTF-8 and compared with every byte of the manuscript snapshot. The reported stored size was also 5,387 bytes, and the SHA-256 values matched.
The simplified check looks like this. This is explanatory pseudocode with the retrieval API and error handling omitted, not a newly validated distribution tool.
expected = bytes of the manuscript snapshot intended for review
observed = complete review-copy text encoded as UTF-8
Check every byte of observed against expected
Compare the reported stored size with the length of expected
Record the SHA-256 of the compared text and the check time
This evidence is a comparison of retrieved UTF-8 text and reported size. It should not be described as a separate raw binary download test of the cloud file.
Check history and sharing separately from content
Before the update, the existing review text was checked against the preserved old draft. The content was then updated under the same file ID. No new public link or sharing destination was created.
The saved records show that the filename, ID, parent location, and nonshared permission state remained unchanged. They also show more than an old revision appearing in a history list: that revision was read back and its complete text matched the preserved old manuscript.
That establishes that the earlier revision was readable at the time of the operation. It does not promise indefinite history retention. The comparison before writing is also not an atomic lock. Safe handling of an edit arriving between the comparison and the write was not established.
If the destination differs from the preserved draft in an unexpected way, there is insufficient evidence to call it merely stale and replace it. Preserve both versions and resolve which one should be used. Avoiding automatic resends after an uncertain outcome is an operational rule here, not the result of a network-fault injection test.
Text identity is not factual review or publication approval
A hash or full-text comparison helps identify what was handed over. It does not establish that the claims are correct, that the prose is clear, or that the author has approved publication.
For this article, I rechecked the saved October 20 operation records and readback text against the manuscripts retained locally. This is not a fresh inspection of the current cloud document. The development tests discussed in the underlying manuscript were not rerun either.
Revising the original does not prove that the review copy was updated. Linking the intended snapshot to the text read back from its destination made that handoff mismatch observable and allowed it to be resolved in this case.
AI assisted the operation's comparison process, the organization of the saved records, and the organization and writing of this article.
Top comments (0)