Remote delivery keeps a local causal anchor
This figure documents the historical i386 source baseline. Current native x86-64/AArch64 qualification is recorded separately; this is not an ELF64 or native SMP implementation diagram.
A transported message carries enough origin context to connect remote ancestry to local delivery.
Text equivalent and source references
- Node A sends target actor, payload, sender node/actor, remote causal ID, Lamport clock and summary hash through the encrypted mesh.
- Node B decrypts and dispatches, merges the remote clock and anchors the remote cause, then attempts local mailbox enqueue. A later receive links local delivery ancestry. Unknown/full destinations fail; bounded retries and retained proofs are not exactly-once delivery.
Sequence diagram. Source paths refer to the atlas baseline; the kernel checkout is private.
include/federation.h · federation_msg_t, retry limitskernel/graph/federation.c · federation receive loopkernel/graph/actor.c · actor_send_remote, actor_recv