M12.4: record and replay exact biological transfer pairs
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m30s
Foundation / checks (client) (push) Failing after 18m38s
Foundation / checks (network) (push) Successful in 22m21s
Foundation / checks (tsan) (push) Failing after 22m17s
Foundation / checks (postgres) (push) Successful in 51m32s
Foundation / checks (checks) (push) Failing after 59m20s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-17 18:23:33 -04:00
parent decd4f8043
commit 1e207b5ee4
13 changed files with 637 additions and 2 deletions
+4
View File
@@ -55,6 +55,10 @@ no admitted durable manifest bundle yet. Existing profile-4/5 publishers retain
their tuples; population trace 1 refuses envelope 2. A future adapter must freeze
the source and atomically commit both fenced heads before destination activation.
See [scope and remaining proof](../engineering/M12_EXACT_BIOLOGICAL_TRANSFER.md).
Its bounded [paired migration trace](../../schemas/cellular-migration-trace-v1.md)
replays from both source cuts and an independently trusted request, including
complete cohort tags. Independent-process replay is qualified; no existing
durable publisher admits that trace or treats it as a transfer receipt.
World/region/frame are nonzero durable IDs. No ID is a Pod name. The host records
its unique holder ID and monotonically increasing nonzero lease epoch. Exhaustion