Files
aevolution/schemas/cellular-population.md
T
dingo 5decaa0326
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 3m16s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (client) (push) Canceled after 13m8s
Foundation / checks (checks) (push) Canceled after 13m12s
Foundation / checks (postgres) (push) Canceled after 13m2s
Foundation / checks (network) (push) Canceled after 13m4s
Foundation / checks (tsan) (push) Canceled after 13m9s
M12.3: persist exact population state and automatic conversion policy
2026-10-17 12:11:10 -04:00

1.6 KiB

Exact cellular population envelope 1

Authority: ADR-0139/0140. Little-endian integers, no padding. Size is bounded by max_cellular_population_bytes. No changes to existing cellular owner envelopes.

Offset Bytes Field
0 8 Magic AEVOPOP1
8 4 Version 1
12 4 Automatic policy flag, exactly 0 or 1
16 4 Materialization radius, micrometres, positive
20 4 Collapse radius, strictly larger, at most 1,000,000 micrometres
24 8 Conversion sequence
32 8 World
40 8 Region
48 8 Frame
56 8 Completed tick
64 8 Nested biological payload bytes
72 8 Cohort member count, at most 256
80 16 each Sorted unique member life ID and exact genome ID
after members declared length Complete canonical rules-8 CellularLives snapshot
final 8 FNV-1a64 over all preceding bytes

Require exact total length, matching trusted identity/tick, valid policy, canonical nested restoration and complete byte-identical re-encoding. Every tagged member must exist, have zero account, active presence and exactly the recorded genome. The membership table contains no additional inventory. Untagged living cells are individuals. New offspring may be individual until the next applicable group conversion. No random seed or residual is missing: the representation is exact.

The checksum detects corruption, not malicious alteration. Production object publication must also bind SHA-256, predecessor, current fence and immutable manifest. This format is not yet an accepted PostgreSQL checkpoint profile; it must never be labeled as the existing cellular profile-4 payload.