Specify durable cellular action identity
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

This commit is contained in:
dingo
2026-10-10 22:51:37 -04:00
parent b25787f8e6
commit d0c7a938f1
6 changed files with 101 additions and 13 deletions
@@ -55,3 +55,12 @@ 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.
+15 -11
View File
@@ -55,12 +55,15 @@ together, and ADR-0107 additionally produces corpses and a heat transfer.
binding. Profile-specific version slots must explicitly pin the cellular
rule, envelope, habitat, coordinate, genome, development, founder and archive
formats before the profile is admitted by `supported()` or PostgreSQL.
- Canonical cellular intentions, final outcomes and exact retries remain in
the existing durable decision/publication records, transactionally bound to
the checkpoint head. They are not a client-authored state section. A session
reconnect never advances biology; only the fenced region owner may publish a
tick. Profile-4 cloning stays unsupported until its identity and source-total
remapping rules are specified.
- Canonical cellular player inputs, final outcomes and exact retries are
transactionally bound to the checkpoint head under
[ADR-0111](0111-cellular-durable-action-identity.md). V6 datagram receipts are
provisional and cannot advance persistent cellular state; the durable host
consumes a reliable v7 action with stable account/action identity. These
records are not a client-authored state section. A session reconnect never
advances biology; only the fenced region owner may publish a tick. Profile-4
cloning stays unsupported until its identity and source-total remapping rules
are specified.
## Alternatives considered
@@ -86,8 +89,9 @@ closed.
## Consequences
Implement the profile codec and restore validator before admitting it to the
manifest allowlist. Then extend the SQL profile parser/caps and add process
publication, uncertain-commit, kill/restart and profile-3 compatibility tests.
Until those gates pass, no cellular state is durably playable and M11.3d/e stay
open.
The profile codec, portable manifest allowlist and bounded SQL parser are now
implemented. The database still rejects progressing profile-4 commits until
the reliable v7 input/result records and dedicated atomic publisher are in
place. Then add uncertain-commit, kill/restart and profile-3 compatibility
tests. Until those gates pass, no cellular state is durably playable and
M11.3d/e stay open.
@@ -0,0 +1,58 @@
# 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.
+2 -1
View File
@@ -8,9 +8,10 @@
- [ADR-0105: Cellular session intention protocol v6](0105-cellular-session-intention-v6.md) - accepted M11.3 wire direction for movement plus an optional food-patch target; v1-v5 remain frozen and v6 has an opt-in admission path.
- [ADR-0106: Cellular contested patch arbitration trial](0106-cellular-contested-patch-arbitration.md) - accepted M11.3 trial resolves same-tick finite-stock claims by stable life identity, independent of connection order.
- [ADR-0107: Cellular starvation and corpse transfer trial](0107-cellular-starvation-and-corpse-transfer.md) - accepted M11.3 death closure transfers body/reserve to a corpse and accumulated heat to the region heat owner.
- [ADR-0108: Cellular life checkpoint profile](0108-cellular-checkpoint-profile.md) - accepted additive profile-4 state-closure direction; codec, SQL admission and recovery remain open.
- [ADR-0108: Cellular life checkpoint profile](0108-cellular-checkpoint-profile.md) - accepted additive profile-4 state-closure direction; SQL publication and recovery remain open.
- [ADR-0109: Cellular region-wide conservation closure](0109-cellular-region-conservation-closure.md) - corrects profile-4 accounting to conserved region totals per channel while retaining patch provenance.
- [ADR-0110: Cellular checkpoint payload bound](0110-cellular-checkpoint-payload-bound.md) - raises profile-4's maximum object size so the complete retained archive and corpse limits fit.
- [ADR-0111: Durable identity for cellular player inputs](0111-cellular-durable-action-identity.md) - specifies the reliable v7 action identity needed for commit-bound cellular outcomes and exact retries.
- [ADR-0058: Region durability contract](0058-region-durability-contract.md) - accepted M7.1 full checkpoint batches and explicit state closure; storage implementation follows.
+7 -1
View File
@@ -91,7 +91,7 @@ scoped change before starting the next segment.
| 11.3a: cellular state and spatial contract | Biology public values; server lifecycle; checkpoint profile; schemas and architecture docs | Implement ADR-0101/0102 microhabitat, movement and contact; define perception range, resource visibility, units, tick order and version allowlist; bounded canonical codec; hostile/truncated inputs refused before allocation; profile-3 compatibility; exact restore of every state field |
| 11.3b: server-authoritative movement and perception | Biology adapter; spatial query; intent validation; network protocol/client session | Clients send only bounded movement/engulf intentions; server decides speed, position, contact and visible environment; range/speed forgery and stale intent tests; deterministic replay |
| 11.3c: metabolism and finite transfers | Biology metabolism/development adapters; cellular field ledger; corpse/predation resolution | Intake and costs derived from phenotype; each resource channel conserves independently; contested stock has one winner; engulfed inventory moves once with excess detritus; starvation and death preserve all inventory |
| 11.3d: durable tick publication and recovery | Primitive region host; persistence adapter/schema; session action outcomes; process tests | Checkpoint, habitat changes, terminal outcome and final action results publish atomically; exact retry after uncertain commit; kill/restart at publication boundaries; no offline progress; Linux/PostgreSQL CI qualification |
| 11.3d: durable tick publication and recovery | Cellular region host; persistence adapter/schema; reliable v7 input and action outcomes; process tests | Checkpoint, habitat changes, terminal outcome and final action results publish atomically; exact retry after uncertain commit; kill/restart at publication boundaries; no offline progress; Linux/PostgreSQL CI qualification |
| 11.3e: exploratory playtest slice | Server view replication; existing engineering client input/view; playtest notes | One player can spawn, see what the cell perceives, steer, seek and feed in a finite habitat; show movement/resource costs and failure states; capture reproducible trace and human notes; no mutation or reproduction implied |
## Required checks
@@ -171,6 +171,12 @@ scoped change before starting the next segment.
and payload cap, rejects clone genesis, and fail-closes progressing profile-4
commits until their dedicated atomic publication path is installed. CI still
needs to execute the migration/parser checks.
- 11.3d-4 contract audit: v6 cellular datagrams have per-session sequence IDs
and only provisional receipts, so they cannot satisfy ADR-0108's exact retry
requirement after reconnect. ADR-0111 keeps v6 frozen and specifies a reliable
v7 action with stable account/action identity and commit-bound input/result
bytes. Durable host work is paused at this contract boundary until the v7
codec and store records are implemented.
## Exit boundary
+10
View File
@@ -6098,3 +6098,13 @@ the environment, MSVC cannot compile the POSIX PostgreSQL integration test
because `poll.h` is unavailable, and `psql` is not installed. The migration and
parser tests were therefore not run locally; per the agreed workflow they must
run in CI. Durable cellular publication remains blocked intentionally.
## 2026-10-10 — M11.3d-4 durable cellular input contract (documentation)
While tracing the profile-4 host path, found that v6's per-session sequence and
provisional admission receipt cannot identify an exact retry after reconnect.
The existing durable action ledger needs stable account/action identity. ADR-0111
records the resolution: preserve v6 unchanged and use a reliable v7 cellular
action whose canonical input and final result commit with the cellular
checkpoint. No implementation or tests were run for this documentation-only
contract; durable host coding follows it.