Record format
realm/1
realm/1 — the Graph layer’s registry: the agent-navigable world above the estate’s houses, where one fetch of /.well-known/realm.json gets a machine every house, its machine door and the Chronicle feed. graph/1 derives its org/ nodes from this manifest; the human side enters through a house and an archetype folded from the same register.
version 0.1.0 · measured 2026-10-19 from a checkout · source: therealm
node vendor-realm.mjs check <file> — dependency-free; not on npmOne register, two faces that cannot disagree: the manifest, the map and the mesh surfaces all fold from src/houses.mjs, and a house is linked (and its surfaces emitted) only when it is live — a map that links to what does not exist teaches a reader the rest cannot be trusted. It also carries identity/1, the RitualOS house-and-archetype taxonomy, with a source track-back rather than a reinvention.
rising/1 is self-declared, not measured: the per-house counts come from the Realm’s own register, so the sealed append-only chain is tamper-evidence for a figure nobody outside the Realm has witnessed — it earns the word measured only once each org’s identity is fetched from that org’s own served surface, and the pages say so.
Edge cases — each one paid for once
Committed is not served, and 403 reads as unread
verify:live fetches every surface the manifest promises and fails on one that answers the wrong document, but a surface returning 403 (Deployment Protection left on) reads as unread — a network fact — not as a broken promise. If the domain’s own well-known 403s, the machine door is shut while every offline test still passes.