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:
dingo
2026-09-29 06:47:45 -04:00
co-authored by Claude Opus 5.5
parent 7aec68db8e
commit 703f67834f
28 changed files with 2206 additions and 266 deletions
+27
View File
@@ -901,3 +901,30 @@ Linux ran 59/59 in four configurations; the PostgreSQL suites passed in three.
Docker itself was not run locally; an emulated image layout was checked instead.
Next: M7.9.
## M7.9a region clones and retained history (2026-09-29)
ADR-0067 adds a consistent clone into an isolated world:
- **Re-identification:** `rebind_world` changes only the recorded world, and the
byte round trip is proven.
- **Schema v7 clone genesis:** it starts at the source tick, names the source
commit and digest, and digests the inherited outcomes.
- **`evo-world-clone clone`:** it reads the source read-only, requires a separate
database and user, and writes the target in one owner transaction.
`audit_region_history` (also `evo-world-clone audit`) re-verifies every retained
link.
Real processes showed:
- after re-identification, the clone and its source followed a byte-identical
trajectory;
- the clone cannot write its source;
- a killed clone left the source untouched and the target not ready;
- a missing historical trace is detected even when head recovery succeeds.
Five mutations were caught. Windows ran 59/59; Linux ran 59/59 in four
configurations; the PostgreSQL suites passed in three.
Next: M7.9b, covering the upgrade barrier and old-writer fencing, schema
migration failure while a host is serving, and measured recovery and batching
latency.