Files
aevolution/docs/adr/0111-cellular-durable-action-identity.md
T
dingo d0c7a938f1
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
Specify durable cellular action identity
2026-10-10 22:51:37 -04:00

3.1 KiB

ADR-0111: Durable identity for cellular player inputs

Status

Accepted engineering contract for M11.3d/e (2026-10-10). This changes no cellular gameplay constants. The user authorized proceeding with recommendations and revisiting decisions after review; implementation and CI remain pending.

Context

ADR-0108 requires canonical cellular intentions, final outcomes and exact retries to commit with the complete cellular checkpoint. The M11.3 v6 cellular intention is a 48-byte datagram whose sequence is scoped to one session. Its admission receipt is provisional, and IntentAdmission discards pending inputs when the session closes. The durable action ledger instead uses stable account/action IDs. It cannot identify a v6 datagram across reconnects or resolve its final result. Using v6 directly to advance persistent biology would therefore leave an uncertain-commit retry ambiguous.

Decision

  • Keep the v6 datagram layout and admission behavior unchanged. A v6 receipt is admission only; v6 is not an input path for persistent cellular state.
  • Add a reliable cellular action in session protocol v7. It carries the authenticated session/epoch, a stable nonzero per-account action_id, the intended tick, bounded movement components, and an optional food-patch address. The exact codec and refusal rules must be specified and tested before server admission is enabled.
  • Reuse the durable account/action identity and query flow for exact retries. The cellular publication adds immutable canonical input bytes and the deterministic final result keyed by (world, account, action_id), bound to the same commit as its profile-4 checkpoint. Reusing an ID with different input is a conflict. Admission stays provisional; success is reported only after the checkpoint transaction is confirmed or resolved.
  • Recovery replays the recorded cellular inputs from the verified predecessor, requires the resulting canonical profile-4 bytes to match the committed object, and reconciles every action outcome with the same commit. Unknown transaction results freeze simulation until exact resolution; reconnect never advances biology.
  • Profile-4 cloning stays unsupported. A one-account/one-life control binding and the existing one-cellular-intention-per-life-per-tick rule remain in force.

Alternatives

  • Persist (account, session, sequence) for v6: rejected because a reconnect creates a new session and its per-session sequence restarts.
  • Treat the v6 receipt or simulated watermark as final: rejected because neither proves that the matching checkpoint transaction committed.
  • Put v6 sequence into the existing action ID without changing its scope: rejected because it can collide across new sessions for one account.

Consequences

M11.3d must implement the v7 reliable input codec, immutable input/outcome publication and replay recovery before a persistent cellular host may consume player input. M11.3e can then test the existing cellular rules without changing their values. ADR-0105 v6 remains a frozen provisional input contract and does not claim durable cellular play.