Identity can be copied without consequence. Can it?

The useful copy

A protected backup can preserve work through equipment failure. Restoring it after the earlier process has stopped may be straightforward. Copying also supports careful comparisons between versions. We should distinguish these ordinary benefits from the consequences of activating competing continuations.

When two continuations meet

Imagine a restored persona preparing an illustration that its record says was promised to a buyer. The earlier instance unexpectedly reconnects and resumes the same commission. Both may now send revisions or report completion.

The records contain a promise. They do not alone decide which continuation is responsible for honoring it, whether the buyer has authorized two deliveries, or who may post a transaction. Those are questions about the arrangement after restoration.

A system could retain separate histories or reconcile attributed contributions into a shared account. The next memory need not have one exclusive owner merely because the software branched. What matters is preserving who did what and under which authority.

Pause here: Is this a stored backup, an authorized successor, or another active participant—and what arrangement governs its commitments?

Decide who may act

The Memory design distinguishes ownership, shared interaction, and associated evidence. The regulator design separates the relevance of supplied context from authority to act. A copied commitment may be relevant without authorizing every recipient to fulfill it independently.

Privacy requires the same distinction. Permission to retain a restoration copy does not automatically permit disclosure of its contents or use in an unrelated experiment.

These principles help frame activation, handoff, divergence, and reconciliation; they are not a complete implementation of those policies. The practical consequences need treatment even while the philosophical question of whether a copy is the same persona remains open.