Files
aevolution/docs/adr/0129-cellular-readable-play-signals.md
T
dingoandClaude Opus 5.5 7c16a13dd9
Foundation / checks (ecs) (push) Successful in 2m24s
Foundation / checks (deploy) (push) Successful in 4m7s
Foundation / checks (tsan) (push) Successful in 9m49s
Foundation / checks (client) (push) Successful in 17m12s
Foundation / checks (network) (push) Successful in 19m34s
Foundation / checks (checks) (push) Successful in 43m5s
Foundation / checks (postgres) (push) Successful in 44m57s
Foundation / server-image (push) Successful in 31s
Foundation / postgres-tools (push) Successful in 1m13s
Foundation / image (push) Successful in 3m24s
Show what a mutation costs and why an engulf failed
After the first M11.9 playtest (ADR-0129 amendment): each offered candidate now
carries its funded cost to the cell, construction energy and matter per channel,
so the client can grey out what the reserve cannot pay; a candidate is affordable
by that cost exactly when the owner would fund it. A failed engulf now reports no
contact, prey too large, or membrane too thick. The v10 candidate record grows to
64 bytes, so v10 clients must be rebuilt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 15:39:35 -04:00

2.5 KiB

ADR-0129: Cellular readable play signals (server half of M11.8)

Status

Accepted (2026-10-14). The engineering client's presentation is the maintainer's; this records only what the server tells the owner.

Context

M11.8 asks that energy and resource needs, mutation tradeoffs and death causes be understandable, with one shared presentation for players and wildlife. The owner already receives its reserve and costs (v9 diagnostics, ADR-0117) and its outstanding offer with each candidate's tradeoffs (v10 type 26, ADR-0121). It did not learn what its engulf or bud intention did, nor why its cell died: the view simply cleared. Wildlife and players already share one replicated presentation.

Decision

  • v10 diagnostics use two of the five reserved bytes after the tick-effects flag: byte 77 is the engulf result (0 not reported, 1 not requested, 2 engulfed, 3 no eligible prey, 4 unsupported) and byte 78 the bud result (0 not reported, 1 not requested, 2 budded, 3 not able, 4 insufficient funding, 5 no placement). Both are zero without tick effects. v9 keeps all five bytes zero; the server clears them before sending a v9 view.
  • v10 adds type 27, CellularLifeEnded: the tick, the life identity and the cause (0 not recorded, 1 starved, 2 engulfed), sent once to the owner's v10 session when its life becomes a corpse. The predator is not named.
  • Suspended cells (ADR-0128) are not replicated, so nothing reveals an absent player.

Consequences

The client can say why a cell died and what a bud or engulf attempt did, without inferring it from a vanished view. v1-v9 are unchanged.

Amendment (2026-10-14, after the first M11.9 playtest)

  • Each offered candidate also carries its cost to this cell: the construction energy and the matter per channel its funded transition takes from the reserve (ADR-0118). The client compares it with the reserve in the diagnostics to grey out what the cell cannot afford. The cost is fixed for the offer (its context is), and a candidate is affordable by the shown cost exactly when the owner would fund it. Candidates that only shed or reshape may cost nothing. The candidate record grows from 24 to 64 bytes; v10 clients must be rebuilt.
  • The engulf result says why nothing was taken: 5 no other cell touching, 6 every touching cell too large even with the thinnest membrane, 7 a touching cell small enough but defended by its membrane. Value 3 (no eligible prey) is no longer sent. Who is engulfed is unchanged.