# M11 primitive-life session protocol, version 5 Version 5 adds the reliable new-life request family to the v4 session protocol. All messages 1–17 retain their v4 layout. Version 4 remains the default for existing regions; primitive-profile servers require v5, while other region servers continue to refuse it. The server binds life requests to the authenticated account-control generation and requires durable account control before accepting v5. A v4 peer rejects types 18–21. Integers are little-endian, the 8-byte `EVSN` header has zero flags, and each message has the exact size below. This schema describes the wire codec only; server admission and durable execution are separate implementation gates. | Type | Direction | Payload | Bytes | |---|---|---|---:| | 18 PrimitiveLifeRequest | client → server, reliable stream | session u64, epoch u64, request_id u64 | 24 | | 19 PrimitiveLifeReceipt | server → client, reliable stream | request_id u64, admission status u8 (0–10), server_tick u64 | 17 | | 20 PrimitiveLifeOutcome | server → client, reliable stream | request_id u64, result u8, life_identity u64, commit_sequence u64 | 25 | | 21 PrimitiveLifeQuery | client → server, reliable stream | request_id u64 | 8 | The server sends `Welcome` in the same protocol version as `Hello`. Every later stream message must use that negotiated version. Primitive-life messages are reliable-stream only; datagrams retain the v4 rules. A request is admitted only when session id and epoch match, the region is ready and durable control is held; the receipt precedes the durable outcome. Queries are read-only and use the same authenticated account and control generation. Result values: 1 born (identity and commit sequence must both be nonzero), 2 insufficient funding, 3 no placement, 4 existing life, 5 cancelled, 6 pending (query only), 7 unknown (query only). Non-born results carry zero identity and commit sequence. A region-control move durably cancels an unpublished reservation; retrying that request returns cancelled and a new request is required. `existing life` is recorded for the conflicting request, so its exact retry/query remains stable. Request IDs are a separate namespace from M10 action IDs. Receipt reports admission only; it does not claim that a life was durably born.