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
@@ -62,6 +62,16 @@ The caller's stable workflow request UUID belongs to that durable I/O journal;
it is not a biological identity or a kernel PRNG decision. Source/destination head
comparison prevents a second application under a different request UUID.
Portable paired trace 1 binds the stable request, both predecessor manifests,
both result commit IDs, representation, common cut, exact group and material.
Replay receives an independently trusted request and both complete source cuts;
it recomputes the paired candidates and verifies recorded membership and flows.
The trace is bounded/canonical and has no ownership authority by itself. The I/O
adapter must validate predecessor manifest/payload digests and journal bindings;
the trace's embedded request cannot supply that trust. Independent-process replay
qualifies the raw and population representations without implying durable escrow.
See [the trace schema](../../schemas/cellular-migration-trace-v1.md).
This primitive changes ownership at an explicitly compatible cut and preserves
coordinates. It does not choose a physical route or let current clamped movement
cross an arena edge. Automatic linked-habitat movement, boundary contacts and