P6 — Registry state sync & replication. Everything P1–P5 built lives in one hash-chained log; the Sync panel below exports that log as a portable bundle and imports bundles from another browser context. Same identity, same state, same receipts — in two independent places. Divergent writes are detected, never overwritten.
Three Weave entities exist as semantic cores in the registry. Seed them once; every world then interprets them through its own manifest.
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.