Foundation / checks (client) (push) Successful in 4s
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / postgres-tools (push) Successful in 5s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 5s
67 lines
3.4 KiB
Markdown
67 lines
3.4 KiB
Markdown
# ADR-0105: Cellular session intention protocol v6
|
||
|
||
## Status
|
||
|
||
Accepted wire-contract direction for M11.3 (2026-10-10). The codec is being
|
||
implemented first; server admission and durable resolution remain separate gates.
|
||
|
||
## Context
|
||
|
||
The deployed session wire versions 1–4 are frozen, and v5 adds only reliable
|
||
primitive-life creation/query messages. In primitive v5 mode the current server
|
||
rejects movement datagrams, probe actions and M10 interest. M11.3 needs a client
|
||
to request bounded movement and choose one nearby food patch without claiming
|
||
position, speed, energy or inventory.
|
||
|
||
## Decision
|
||
|
||
- Add session protocol v6 while preserving the exact v1–v5 encodings. V6 retains
|
||
the existing session, control epoch, movement vector, sequence and scheduled
|
||
tick fields, and adds an optional target patch address in micrometres.
|
||
- The v6 `CellularIntention` is a fixed 48-byte little-endian datagram payload.
|
||
The strict layout and canonical absent-target form are in
|
||
[session-v6-cellular-intention](../../schemas/network/session-v6-cellular-intention.md).
|
||
- The target is an intention only. The server checks authenticated session and
|
||
epoch, tick and sequence window, movement norm, patch alignment and visibility;
|
||
it resolves position and contact, then derives any costs or acquired stock.
|
||
- A cellular client must negotiate v6 explicitly. The current session server
|
||
remains unchanged until it has a cellular handler; the codec alone does not
|
||
authorize gameplay.
|
||
|
||
## Alternatives considered
|
||
|
||
- **Reuse the M10 marker intention:** rejected because its simulation path moves
|
||
a non-biological probe at a fixed speed and has no energy, habitat or life.
|
||
- **Send a position or inventory delta:** rejected because it would let the
|
||
client claim authoritative state.
|
||
- **Change v5 in place:** rejected because v5 life creation is an existing
|
||
versioned contract and must retain its exact bytes and primitive-only scope.
|
||
|
||
## Consequences
|
||
|
||
V6 provides a bounded, explicit wire value for the next server integration. It
|
||
does not implement admission, durable tick publication, a life view, client UI
|
||
or cross-region owner routing; M11.3 remains incomplete until those pieces work
|
||
end to end.
|
||
|
||
## Amendment (2026-10-10, M11.3b-5): opt-in session admission
|
||
|
||
`RegionSessionsConfig::accept_cellular_intentions` enables v6 login and routes
|
||
cellular datagrams through the existing bounded intention admission. The host
|
||
can read deterministic scheduled inputs before advancing the simulated tick;
|
||
receipts and cumulative simulated watermarks use the negotiated v6 encoding.
|
||
`RegionSessionClient` can send v6 movement and an optional patch address. The
|
||
setting defaults off, and primitive-life v5 remains mutually exclusive. This
|
||
does not connect those inputs to cellular state, durable publication or client
|
||
perception. V6 sessions cannot request the M10 probe replication view or receive
|
||
probe markers until a cellular perception view is available.
|
||
|
||
## Amendment (2026-10-10, durable input audit)
|
||
|
||
The v6 sequence is scoped to one authenticated session, and pending v6 inputs
|
||
are in memory only. Its admission receipt and simulated watermark do not prove
|
||
that a cellular checkpoint transaction committed. Under
|
||
[ADR-0111](0111-cellular-durable-action-identity.md), v6 remains wire-frozen and
|
||
provisional; persistent cellular play uses a later reliable action contract with
|
||
a stable account/action ID and a commit-bound result.
|