sow-tools

ShadowsOverWestgate/sow-tools

Fork 0

Author	SHA1	Message	Date
archvillainetteandClaude Opus 5	3bf2031c2e	docs(nwsync): verify is what tells you which keys to purge ci / ci (pull_request) Successful in 3m29s Details Running the repair for sow-tools#88 disproved the advice #90 had just landed. "Purge the zone, then believe verify" assumed the stale set was unknowable. It is not: verify reads the edge, so a run straight after a repair names every key the edge is still serving stale — a survey, not a verdict. Purge those, re-run, and the second run is the verdict. The measured numbers are the argument. The repair rewrote 2,603 blobs at the origin; 8 were stale at the edge, all of them ones a failed player sync had pulled ninety minutes earlier. The edge only caches what someone fetched, so purging the whole zone would have cooled 69,169 objects to fix 8. Refs #88, #89, #75. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-01 09:00:20 +00:00

Author

SHA1

Message

Date

archvillainetteandClaude Opus 5

3bf2031c2e

docs(nwsync): verify is what tells you which keys to purge

ci / ci (pull_request) Successful in 3m29s

Details

Running the repair for sow-tools#88 disproved the advice #90 had just
landed. "Purge the zone, then believe verify" assumed the stale set was
unknowable. It is not: verify reads the edge, so a run straight after a
repair names every key the edge is still serving stale — a survey, not a
verdict. Purge those, re-run, and the second run is the verdict.

The measured numbers are the argument. The repair rewrote 2,603 blobs at
the origin; 8 were stale at the edge, all of them ones a failed player
sync had pulled ninety minutes earlier. The edge only caches what someone
fetched, so purging the whole zone would have cooled 69,169 objects to
fix 8.

Refs #88, #89, #75.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-01 09:00:20 +00:00

Compare commits

Diff Content Not Available