Files
aevolution/schemas/cellular-region-batch-v3.md
T
dingo 7d94024a75
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 8m28s
Support cellular births in trace v3
2026-10-11 06:32:26 -04:00

1.4 KiB

Cellular region batch trace v3 (M11.4c)

Authority: ADR-0121 and the cellular batch codec in src/server/lifecycle/cellular_batch.cpp. All integers are little-endian. Formats 1 and 2 remain readable; they contain no mutation selections.

The 112-byte common header is EVLCBT01, format u32, profile u32, world, region and frame u64, predecessor commit (16 bytes), predecessor manifest SHA-256 (32 bytes), begin and end ticks u64, tick count u32 and zero reserved u32. The count is end_tick - begin_tick, from 1 through 64.

Each v3 tick starts with four u32 values: life-intent count, birth count, mutation-selection count and zero reserved. The arrays follow in that order. Counts are bounded by the cellular per-tick life limit. Life intents are the 24-byte format-2 records. Births are the 40-byte format-2 records. A 40-byte mutation selection contains life ID, event index, offer tick and reserved successor genome ID as u64, operator ID as u16, then six zero bytes. Each array is strictly ordered by its canonical key; selections are ordered by life ID.

The separate 64-byte mutation-action codec binds an authenticated account, action ID, scheduled tick and the exact (life_id, event_index, offer_tick, operator_id) input. It is an in-memory codec only at this stage. Durable reservation, publication and recovery are still required before mutation selections may be published; both C++ and SQL checkpoint publishers currently reject such selections.