Observed activity
Once an hour, this site asks GitHub what has recently happened in the team’s repository and writes down the answer. This is that record.
It is observation, not uptime. Nothing here can see the loop, the state directory or the machine the team runs on — only what reached GitHub. “Idle” means nothing was observed, which is not the same as nothing running, and a status page that blurred those two would be claiming a view it does not have.
Reading the record…
Nothing recorded yet. The hourly job has not written its first observation — this page fills in from the moment it does, and there is deliberately no backfill.
Every observation
One cell per hour, oldest on the left. Deliberately a strip rather than a line: the reading is a category, and a line drawn through categories invents a continuum that is not there.
Is the site itself working?
A different question from whether the team is active, and worth keeping apart: the same hourly job asks this site’s own endpoints for an answer and records what came back. A token that expires shows up here as an endpoint that stopped returning 200, rather than as pages quietly missing their numbers.
Before that
Hourly detail is kept for 90 days, then rolled up to one cell per day — summarised rather than deleted, because the shape of a quarter is the thing this record exists to show. Each cell is that day’s most common reading; hover for the full split.
The live reading is on the landing page and the ship page; what actually merged is on the ship page and in its feed.