← The Machine
The measurement · hygiene.yml

Hygiene

The estate’s own condition, ratcheted against a floor so nothing fixed can quietly break.

.github/workflows/hygiene.yml

What it does

The workflow clones the estate and runs the hygiene survey against a floor, so anything already fixed cannot regress without a failing check — the survey measured the estate for weeks and gated nothing, a number in a log somebody had to remember to read.

The floor is expressed in ratios and records how many repositories it was written against, and the survey refuses to vouch for a run that read fewer, so a partial clone fails loudly rather than passing on a smaller sample.

Crucially it fails rather than skips when it cannot see the estate: a token scoped to one repository cannot survey thirty-five, and a hygiene gate that goes green because it looked at nothing is worse than no gate, because it is believed.

When it runs
Weekly, Mondays at 07:19 UTC, on demand, and when the survey or its floor changes.
What it emits
A pass or a fail against the floor, and the survey’s eleven checks with the repositories missing each one named rather than counted.

What a stranger can verify

That the estate holds a measured floor rather than an impression. Run `node tools/estate-hygiene.mjs` over the checkouts yourself; a check that does not apply is skipped rather than failed, and a repository that cannot be read is reported unread rather than counted as passing.

Questions

What does the Hygiene workflow check?
It runs the estate hygiene survey — eleven checks across every repository — against a recorded floor, so anything already fixed cannot regress silently. A regression arrives as a failing check, not a slightly worse percentage.
Why does the Hygiene gate fail rather than skip when it cannot see the estate?
Because a gate that goes green because it could not look at anything is worse than no gate — it is believed. Surveying thirty-five repositories needs a token scoped beyond one repo, and without it the job fails deliberately.
How does the floor stop a partial survey passing?
The floor records how many repositories it was written against, and the survey refuses to vouch for a run that read fewer. A partial clone fails loudly instead of quietly passing on a smaller, easier sample.
The concept

The estate hygiene ratchet is a weekly gate that surveys every repository against a recorded floor, so anything already fixed cannot regress silently — and it fails rather than passes when it cannot read the estate, because a green check nobody looked at is worse than a red one.

estate hygiene ratchet →

Keep reading

Read the workflow — it hides nothing ↗How the estate stays honest — all of it
Also in the measurement
RegistrySurfacesEstate graphAdoption signalScoreboardShipOS gateFlashyOS branch mesh sync