Running the repair disproved the advice #90 landed an hour earlier.
"Purge the zone, then believe verify" assumed the stale set was unknowable. It is not. verify reads the edge, so the 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 whole argument:
blobs rewritten at the origin
2,603
blobs stale at the edge
8
All eight were ones a failed player sync had pulled ninety minutes before the backfill. The edge only caches what someone fetched, so purging the zone would have cooled 69,169 objects to fix 8.
Full sweep after the targeted purge: verified 69177 of 69177 blobs behind 72544 resources: 0 failures, 14887519535 bytes checked. #75's gate is met.
Running the repair disproved the advice #90 landed an hour earlier.
"Purge the zone, then believe `verify`" assumed the stale set was unknowable. It is not. `verify` reads the edge, so the 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 whole argument:
| | |
| --- | --- |
| blobs rewritten at the origin | 2,603 |
| blobs stale at the edge | **8** |
All eight were ones a failed player sync had pulled ninety minutes before the backfill. The edge only caches what someone fetched, so purging the zone would have cooled 69,169 objects to fix 8.
Full sweep after the targeted purge: `verified 69177 of 69177 blobs behind 72544 resources: 0 failures, 14887519535 bytes checked`. #75's gate is met.
Docs only. Runbook side in sow-platform.
Refs #88, #89, #75.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
archvillainette
scheduled this pull request to auto merge when all checks succeed 2026-08-01 07:32:28 +00:00
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
xtul
Running the repair disproved the advice #90 landed an hour earlier.
"Purge the zone, then believe
verify" assumed the stale set was unknowable. It is not.verifyreads the edge, so the 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 whole argument:
All eight were ones a failed player sync had pulled ninety minutes before the backfill. The edge only caches what someone fetched, so purging the zone would have cooled 69,169 objects to fix 8.
Full sweep after the targeted purge:
verified 69177 of 69177 blobs behind 72544 resources: 0 failures, 14887519535 bytes checked. #75's gate is met.Docs only. Runbook side in sow-platform.
Refs #88, #89, #75.
🤖 Generated with Claude Code
ed97cf3d17to3bf2031c2e