P10 — Leaving the laboratory. Five worlds now stand on the protocol: Haven and Emberworks, Saltmarsh (written from the World API alone, P7), and two more independent worlds — Orrery and Underbough — written from the contract alone by implementers who never saw this code. P9's sameness still governs every world: memory is a slice of the one hash-chained log, the fingerprint is the identity of that state, and the log's receipts pin the manifest versions each world acted under. And because a replaced history can be perfectly self-consistent, the hub now offers an anchor: a witness record you hold outside the registry, against which the chain can later be checked.
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.
Local checks prove this registry's history is coherent — never that it is the history that actually happened: a wholesale replaced history can be perfectly self-consistent. An anchor is a small record of the chain's head, captured now and held outside this registry (copy it somewhere the registry cannot rewrite — another device, a message to yourself, paper). Later, verification asks one question: does the chain still pass through the witnessed point? CONSISTENT = the witnessed history is intact (anything after it is unwitnessed extension) · DIVERGED = the history the witness saw is not the history now presented · CHAIN_INVALID = the chain fails its own checks · IDENTITY_MISMATCH = a different Weave identity. No anchor = unwitnessed: possibly fine, provably nothing.
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.