Complete M7.9a region clones and retained-history audit
Clone a verified committed head into an isolated world and database (ADR-0067): world re-identification with a proven byte round trip, a schema v7 clone genesis naming the source commit and digest with digested inherited outcomes, a read-only source session, an owner-only atomic target transaction and the evo-world-clone tool. audit_region_history re-verifies every retained link. Real-process tests cover trajectory equality after the cut, source isolation, killed clones and retention. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -124,8 +124,29 @@ else. Upgrading a v3/v4 database that has published checkpoints (not just
|
||||
genesis) is refused with EVL10 and leaves it unchanged: re-provision those regions,
|
||||
or wait for an explicit legacy-history conversion.
|
||||
|
||||
There is no operator CLI for provisioning yet, and no real world has been
|
||||
provisioned. Migrating v2→v3 fails closed if any v2 head exists, because v2 heads
|
||||
Schema v7 (ADR-0067) adds clones:
|
||||
- `region_origins`, immutable (EVL09);
|
||||
- the owner-only `provision_region_clone`;
|
||||
- clone-genesis parsing, and a head constraint that allows sequence 0 at the
|
||||
cloned tick.
|
||||
The runtime function set is unchanged.
|
||||
|
||||
Clone with `evo-world-clone clone`:
|
||||
- Use a **separate target database** with its own runtime group and login, and
|
||||
migrate it with that group as `EVO_PG_RUNTIME_ROLE`.
|
||||
- Retain the source's build identity in the target before cloning.
|
||||
- The source connection is the source runtime login (read functions only). It is
|
||||
switched to read-only transactions.
|
||||
- The target connection is the target owner.
|
||||
- The tool refuses the same database or the same user on both sides.
|
||||
|
||||
A clone world never receives original regions, and an original world never
|
||||
receives clones. `evo-world-clone audit` verifies a region's whole retained
|
||||
history; it is read-only and needs only runtime read access. Never point a clone
|
||||
target at a production database or World0.
|
||||
|
||||
There is no operator CLI for provisioning original regions yet, and no real world
|
||||
has been provisioned. Migrating v2→v3 fails closed if any v2 head exists, because v2 heads
|
||||
have no payload.
|
||||
|
||||
## Host lease discipline
|
||||
|
||||
Reference in New Issue
Block a user