← The Machine
The record · estate-record.yml

Estate record

The estate’s two tenses, merged from the live sites and never from these checkouts.

.github/workflows/estate-record.ymlruns @flashyos/shiplog

What it does

The workflow builds the directory, verify, backlog and shiplog packages, then merges the estate’s past and future tenses — `shipped/1` and `backlog/1` — from what each property serves at its own domain, not from any local checkout.

The distinction is the whole point of federation. A merge assembled from local files would prove only that they sit on one runner, and worse, it would merge the private tier: a checkout carries a repository’s full record while its served fragment carries only what somebody chose to publish.

The result is committed so a property that stops publishing shows up as a line changing from present to absent in a diff, rather than only in a log nobody reads.

When it runs
Daily at 05:37 UTC, on demand, and when the merge script, the domain list or the two tense packages change.
What it emits
A committed `estate-shiplog.json` and `estate-backlog.json`, and their served copies under `apps/marketing/public/`, assembled over the network from published fragments.

What a stranger can verify

That the estate’s merged record is only what the domains actually serve. Fetch the same public fragments the merge reads and re-run the merge yourself; a property that publishes nothing contributes nothing, and the diff says so.

Questions

Why is the estate record merged from live domains, not local files?
Because a merge of local files proves only that the files are on one machine, and it would leak the private tier — a checkout holds the full record while the served fragment holds only what was chosen to publish. Federation is the point.
How does the estate record show a property that stops publishing?
The merged file is committed, so a property going dark shows up as a line changing from present to absent in a diff — the same reason the registry and the scoreboard are committed rather than logged.
What are the two tenses in the estate record?
The past tense is shipped/1, one sealed entry per thing that shipped; the future tense is backlog/1, one decaying item per intention. The workflow merges both across the estate from what each domain serves.

Keep reading

Read the workflow — it hides nothing ↗The format it keeps current: @flashyos/shiplogHow the estate stays honest — all of it
Also in the record
Shiplog