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
+15
View File
@@ -220,3 +220,18 @@ after commit but before acknowledgement, and after acknowledgement.
A SIGSTOPped owner resumed fenced: it was not ready, refused admission and
acknowledged nothing new. Corrupt payloads and missing traces quarantined with
no fallback. Host loss and clone or migration remain M8 and M7.9.
M7.9a (ADR-0067) clones a verified committed head into another world and
database:
- The payload is re-identified, and the byte round trip is proven.
- The clone genesis names the source commit and digest, and inherits the source's
outcomes and ancestry.
- The source session is read-only.
- A clone killed before its target transaction left the source untouched and the
target unprovisioned (it quarantined rather than serve), and a retry completed.
- The same inputs from the cut reproduced the source trajectory exactly.
`audit_region_history` re-verifies every retained link across owners and kills.
It names the exact link whose evidence is missing, even though head recovery
still succeeds. Migration, fencing of old writers, and measured recovery and
batching latency are still M7.9b.