# 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.