Files
aevolution/schemas/primitive-batch-v1.md
T
dingo 41237bd289
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m53s
Foundation / checks (checks) (push) Failing after 4m11s
Foundation / checks (tsan) (push) Canceled after 0s
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 4m28s
Foundation / checks (network) (push) Canceled after 6m39s
Foundation / checks (client) (push) Canceled after 8m43s
Add bounded funded-birth batch replay (M11.2c-2a)
2026-10-10 04:51:30 -04:00

2.4 KiB

Primitive creation batch v1

M11.2c-2 portable replay evidence for ADR-0100. This format alone does not register a durable checkpoint profile or authorize a spawn. It records only funded births; later biological actions require an explicit format/rules extension.

All integers are little-endian unsigned. Exact length is 112 + count * 48. No padding, trailing bytes or unknown versions are admitted. The enclosing checkpoint must bind the entire trace by SHA-256; there is no independent checksum.

Offset Bytes Meaning
0 8 Magic EVLIFTB1
8 4 Format 1
12 4 Birth count, 0..256
16 24 World, region, frame (three u64, nonzero)
40 16 Predecessor commit, nonzero
56 32 Predecessor manifest SHA-256, nonzero
88 8 Begin tick, exclusive
96 8 End tick, inclusive; begin < end <= begin + 64
104 8 Reserved zero
112 48 each Birth records

A birth is account bytes[16], new-life request u64, allocated identity u64, control generation u64, and birth tick u64. Account and all identity/control values are nonzero. Birth ticks lie within the batch. Records are strictly ordered by (tick, account bytes, request), with unique accounts and identities. The shared allocated value names four distinct namespaces: life, organism, genome and founding event. It is never a client-chosen identity.

Replay checks region scope and that existing births precede the batch. It restores a detached copy and calls funded creation for every record. Any refusal discards the entire candidate. A successful retry is not admitted as a new birth. Replay uses the recorded order for deterministic placement and funding. The caller must compare the resulting canonical snapshot with the proposed payload.

The owner's checkpoint tick is stored in its manifest. An empty creation batch may advance that tick while all biology remains unchanged; it implies no offline progress, reserve consumption or biological timer advancement. Before replay, the caller must match predecessor commit, predecessor digest and begin tick with the trusted committed head. These chain checks and durable control/reservation validation belong to publication, not to this storage-free codec.

Existing environmental trace formats and payload goldens are unchanged. Durable profile registration, atomic life publication and session integration remain separate delivery subsections.