P9 — Persistent world state. Every world remembers: its memory is a slice of the one hash-chained log, its fingerprint is the identity of that state, and the log's own receipts pin the manifest versions each world acted under — so the hub can say whether the world you return to is the same world you left. The registry's persistence is journaled and self-validating: a crash can cost you the last write or nothing, never a torn world.
Three Weave entities exist as semantic cores in the registry. Seed them once; every world then interprets them through its own manifest.
A world keeps no private store: its memory is derived from the registry log on every read. The fingerprint is the deterministic identity of that memory under the world's manifest — reload the page and it must not change. Continuity is judged against the manifest versions the log's own receipts pinned.
One action: a failure drill on one entity (injected binding failure → rollback, state verified), then every entity in the avatar's current world crosses through the portal — translation and escrow inside it — and the avatar follows. Refused entities stay behind, receipted; a rollback aborts the whole journey before the avatar moves.
Export produces a bundle of this context's whole registry log. Carry it to another browser (file, clipboard, message) and import it there. Import verifies the chain first, then: identical → up to date · bundle older → ignored (state never rolls back) · bundle extends this history → adopted · both sides wrote since the last sync → conflict, nothing overwritten. Rule of the road: mutate → sync → mutate → sync.
Properties dropped by degraded crossings are held here — registry-side, hash-linked to the crossing that dropped them. HELD = awaiting reclaim in a world that maps the class; CLAIMED = restored (hash-verified) and consumed.
| # | Event | Detail | Hash |
|---|
Every entry — including translation attempts and refusals — is hash-chained to the one before it.