# 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. ADR-0157 also allows portable batch 2 replay against envelope 2/owner 7/rules 9. Recorded intentions are unchanged; the bound predecessor's explicit rules field selects maturation. Both raw and cohort replay perform the same funded growth and preserve exact member tags and stocks. This is not durable rules-9 admission; the rules-8 bundle allowlist remains unchanged. ADR-0158/schema 53 subsequently admits this same batch-2 layout under bundle 11, after an explicit retained bundle-10 maturation upgrade. Full recorded growth replay and exact cohort boundaries remain required. No trace format is reinterpreted. 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. ## Portable batch 3 [ADR-0171](../docs/adr/0171-retained-plan-exact-populations.md) adds magic `AEVOPBT3`, version 3, paired only with population envelope 3/owner 8/rules 10. Keep this header, work bounds and exact membership-boundary layout. Biological intervals contain raw trace 4, never trace 3. Manual no-tick conversions contain no raw trace. Fully suspended controlled cells retain frozen-only inputs; birth requests and mutation selections remain forbidden in unattended batches. Recording uses the unchanged wildlife controller and replay uses its retained intentions. The full nested owner retains plans, real paid offspring, stocks and history through every exact boundary. Wrong outer/nested trace pairs or altered boundaries fail without modifying the source. This portable codec adds no SQL allowlist, durable population tuple, destination activation or automatic upgrade.