Files
aevolution/schemas/cellular-population-batch.md
T
dingo 1b5c0cdf7c
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m23s
Foundation / checks (network) (push) Successful in 21m4s
Foundation / checks (client) (push) Successful in 22m15s
Foundation / checks (tsan) (push) Successful in 23m3s
Foundation / checks (postgres) (push) Successful in 51m33s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 55m18s
M12.4: admit and replay durable boundary-accounting upgrades
2026-10-18 08:13:36 -04:00

4.1 KiB

Exact population batch 1

Authority: ADR-0142. All integers little-endian; no padding. Maximum 1,968,376 bytes. This trace belongs only to checkpoint profile 5, nested cellular bundle 9 and history profile 5. SHA-256 binds the complete immutable trace to its manifest.

Offset Bytes Field
0 8 Magic AEVOPBT1
8 4 Format 1
12 4 Kind: 0 biological interval, 1 manual conversion
16 24 World, region, frame as u64
40 16 Predecessor commit UUID
56 32 Predecessor manifest SHA-256
88 16 Begin and end tick as u64
104 4 Boundary count, 1..64
108 4 Reserved, zero
112 8 Nested biological trace length
120 8 Manual conversion genome, zero for kind 0
128 8 Manual destination: 0 individual, 1 cohort; zero for kind 0
136 declared length Unchanged cellular batch format 3 (kind 0 only)
after biology variable Ordered boundaries

Each boundary is conversion sequence u64, member count u64 (0..256), then sorted unique (life u64, genome u64) pairs. Exact end of input and canonical re-encoding are required. Kind 0 has one boundary per tick and advances 1..64 fixed 50 ms ticks. Both headers must agree exactly. Birth and mutation arrays are empty; every controlled cell has exactly its frozen-only intent. Recorded wildlife intentions replay through the same biological kernel. The persisted policy must reproduce the exact boundary, including sequence and every member.

ADR-0143 further restricts new interval preparation/publication to fully suspended controlled cells. Linger remains vulnerable under the existing rules and stays on profile 4. Earlier recorded frozen/lingering traces still decode and replay unchanged for retained recovery; their wire format is not reinterpreted.

Kind 1 contains no biological trace, one boundary and a nonzero genome; begin and end tick are equal and nonzero. Conversion moves the whole eligible wildlife genome group. It cannot change biological bytes or select a random sample.

Profile transitions 4 to 5 and 5 to 4 are separate no-tick commits with no trace. Their immutable SQL evidence binds both source digests and profiles; recovery loads and verifies both payloads. A biological interval or manual conversion instead requires full recorded trace evidence, replay and exact payload equality. Runtime cannot publish either case through the generic region publisher.

Portable batch 2 after biological transfer

ADR-0144 adds magic AEVOPBT2, format 2, with this identical bounded layout. It requires population envelope 2 containing owner 7/rules 8, including its boundary flows and nonresident history. Batch 1 requires envelope 1/owner 6. Magic and full u32 version must agree; cross-version replay is refused before executing biology. Existing batch-1 bytes and replay semantics are unchanged.

Preparation selects the trace version from the owned envelope. Batch 2 records the same complete frozen/wildlife intentions and cohort boundaries. Biological advancement conserves each owner's current stock and preserves cumulative flows; death or representation conversion cannot spend that metadata. Manual conversion retains the same no-tick whole-group contract. No new biological rule or missing random/residual state is introduced.

Batch 2 is portable replay support only. Durable bundle 9's C++ prepared-commit validator and schema 45's SQL trace checker admit only batch 1. A new durable bundle/upgrade and exact history/recovery contract remain required before any publication, scheduling or transfer activation can use the new representation.

M12.4g/schema 46 adds the dedicated bundle-9 to 10 upgrade and full recovery contract. Bundle 10 admits batch 2 for ordinary intervals and manual conversion; bundle 9 still refuses it and remains bound to batch 1. Actual SHA-256 and wire magic/version bindings are checked before SQL's parser-local normalization; stored bytes and retry identities are unchanged. Interval admission/settlement and player-operation materialization keep their existing meaning. Paired transfer trace 1 remains unadmitted and this adds no destination activation rights.