← The Machine
The measurement · graph.yml

Estate graph

One graph, assembled from what properties actually publish rather than from any checkout.

.github/workflows/graph.ymlruns @flashyos/directory

What it does

The workflow fetches every published directory fragment over the network and merges them into one estate graph — not read from this checkout. A graph built from local files proves the files are on one machine; a graph built from published URLs proves the estate publishes what it claims and can be reproduced by somebody who does not trust us.

It is also the only shape that lets a node the estate does not own ever join, because federation resolves an authority per repository rather than assuming one build.

A source that cannot be reached is reported and skipped, never silently dropped: a graph that quietly shrinks when a host has a bad afternoon is worse than one that fails loudly, because everything downstream reads it as fact.

When it runs
Daily at 05:41 UTC, on demand, and when the graph source list or the directory package changes.
What it emits
A committed `graph.json` under `apps/marketing/public/`, assembled over the network from every reachable published fragment.

What a stranger can verify

That the graph is only what the domains publish, and that provenance is a citation to a declared emitter rather than to nothing. Fetch the same published fragments and re-assemble; an edge signed by an id no fragment declares is a citation to nothing, and the measure says so.

Questions

How is the estate graph assembled?
By fetching every published directory fragment over the network and merging them, never from local checkouts — so the graph proves the estate publishes what it claims and can be reproduced by someone who does not trust us.
What happens when a fragment source is unreachable?
It is reported and skipped, never silently dropped. A graph that quietly shrinks when a host has a bad afternoon is worse than one that fails loudly, because everything downstream reads the graph as fact.
Why does the estate measure the share of cross-property edges?
Because it is the honest test of one graph: every other number can be raised by a property talking more about itself. The share of edges that cross a property boundary cannot, so it is the one that resists inflation.
The concept

The estate graph is one entity-and-relationship graph assembled from what properties actually publish over the network, not from any checkout — so it proves the estate publishes what it claims, and reports the share of edges that cross a property boundary as the honest test of one graph.

estate graph →

Keep reading

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