← The Machine
The measurement · scoreboard.yml

Scoreboard

The estate grades itself in public, read from the live sites the way a stranger would.

.github/workflows/scoreboard.ymlruns @flashyos/countersign

What it does

The workflow reads the estate’s own grade through the public audit endpoint — the same way a stranger would — with no checkout of the other repositories, because a scoreboard assembled from local files proves only that the files are on one machine.

A snapshot nobody refreshes is exactly the stale claim this product exists to argue against: it would sit there dated August while the estate changed underneath it, which is the failure the `expires` field was invented to make visible.

It opens a pull request rather than committing to main, because the scoreboard is a claim the estate makes in public and a human should see it change — and the run ignores its own timestamp moving, so it does not open an empty PR every week.

When it runs
Weekly, Mondays at 06:00 UTC — before anyone reads it, after the week’s deploys — and on demand.
What it emits
A pull request updating `estate-scoreboard.json` and its served copy, opened only when a real figure moved: claims, dated, countersigned, independent or grade.

What a stranger can verify

That the grade is read live, not asserted. The scoreboard is assembled through the public audit endpoint anyone can call, and the workflow refuses to open a PR when only its own read timestamp changed — so a moved number is a real change, not a refresh.

Questions

How is the estate scoreboard produced?
By reading the estate’s grade through the public audit endpoint the same way a stranger would, with no checkout of the other repositories — because a scoreboard built from local files proves only that the files are on one machine.
Why does the Scoreboard workflow open a pull request instead of committing?
Because the scoreboard is a claim the estate makes in public, and a human should see it change. It opens a PR only when a real figure moved, ignoring its own read timestamp so it never opens an empty one.
Why refresh the scoreboard on a schedule?
A snapshot nobody refreshes is the stale claim this product argues against — dated August while the estate changes underneath it. Weekly refresh keeps the public grade current rather than quietly wrong.

Keep reading

Read the workflow — it hides nothing ↗The format it keeps current: @flashyos/countersignHow the estate stays honest — all of it
Also in the measurement
RegistrySurfacesEstate graphAdoption signalHygieneShipOS gateFlashyOS branch mesh sync