One page per sweep phase, in the order /health lists them. Each phase's row on /docs/checks links here.
The catalogueEvery ten minutes, after the upvote integrity pass and before the search index is built from it. · stale after 30 minutes
What a visitor sees
The front page and the catalogue API answer from the last catalogue computed, and say so: the moment under the heading ("as of HH:MM UTC") stops moving. A listing published since is not on the front page. /health reports catalogue stale after thirty minutes.
Re-fire
/internal/openproduct/catalogue/rebuild
Recovered
The moment on the front page moves again and /health reports catalogue healthy with a lastRunAt inside the last thirty minutes.
Search indexEvery ten minutes, when a listing has changed since the last build. · stale after 30 minutes
What a visitor sees
Search answers from the last index built: a listing published since is not found by its own name, and the search page says nothing about why. The catalogue can be current while the index is not — they are separate phases, and the index is built from the catalogue in the same tick.
Re-fire
/internal/openproduct/search/rebuild
Recovered
The newest published listing is found by its slug on an anonymous search, and /health reports searchIndex healthy.
Upvote integrityHourly. · stale after 3 hours
What a visitor sees
Every count on the site is the last discount computed: an upvote cast since is counted raw until the next pass, and a listing's clean-votes mark does not move. A dash (—) on a count is a different thing — it means never measured, and the legend on /docs/checks says which is which.
Re-fire
/internal/openproduct/endorsements/integrity-sweep
Recovered
/health reports integrity healthy with a lastRunAt inside the last three hours, and the counts move on the next front-page read.
Automatic checksEvery six hours. · stale after 18 hours
What a visitor sees
Nothing, by design: the detectors raise flags for a person to read and remove nothing, so a stale defence sweep is a reports queue quieter than the week deserves. /health reports it stale after eighteen hours.
Re-fire
/internal/openproduct/defence/sweep
Recovered
/health reports defence healthy, and the reports queue gains whatever the week held.
The day's boardEvery ten minutes; a day's numbers close shortly after midnight UTC. · stale after 30 minutes
What a visitor sees
The day's board and the leaderboard stop moving: a launch that fired today is not placed, and yesterday's numbers may not have closed. The launches strip on the front page shows the last ranking it had.
Re-fire
/internal/openproduct/launches/board-sweep
Recovered
The board's ranking moves and /health reports board healthy.
The weekly digestEvery ten minutes, doing work once a week. · stale after 30 minutes
What a visitor sees
The digest archive says nothing launched this week, and nobody who asked for the email gets one. The page is honest about what it has and silent about what it missed.
Re-fire
/internal/openproduct/digest/queue
Recovered
The week's digest page exists with its launches on it, and /health reports digest healthy.
Daily snapshotsEvery ten minutes, doing work once a day — the first tick after midnight UTC. · stale after 72 hours
What a visitor sees
A listing page's "what changed this week" compares against a snapshot up to three days older than it should be, then says there is no earlier snapshot. Not wrong, only wider; two missed days in a row is the alarm.
Re-fire
/internal/openproduct/snapshots/sweep
Recovered
/health reports snapshots healthy with a lastRunAt inside the last day.