Can a stranger actually read what this estate says it publishes.
The workflow points the estate’s own verifier at the estate’s own live domains and fetches every mesh surface each says it serves — the AAO charter, the directory fragment, the front door, the record projections.
Every other check in the estate compares a file to another file in the same checkout, which proves a file is committed — not the property anyone cares about. Four times in one week a mesh file was committed, passed its check, and 404’d in production; not one was caught by a repository.
It fails on a 404 — a property not serving what it says it does — but not on unreachable, because that is a statement about the network between the runner and the host, and failing on it would train everyone to ignore the job.
That the served bytes exist, not just the committed ones. Fetch any advertised well-known surface from the domain yourself; the job asks the network exactly as a stranger would, and a 404 fails it while a committed-only file passes nothing.
Served, not merely committed is the property a mesh file has only when a stranger can actually fetch it from the domain that promises it — not when it passed an in-repository check. A file can be committed, validate against its format, and still return 404 in production, which no push-triggered check can observe.
served, not merely committed →