Files
aevolution/docs/engineering/M11_6_DELIVERY_PLAN.md
T
dingoandClaude Opus 5.5 4130092d7a End dead lives durably so a player can start again
M11.6a (ADR-0127, schema v37): a published life is marked ended once, by a
commit of its region, through the lease-fenced end_cellular_lives. One active
life per account replaces one life per account, so after a death the account
reserves and publishes a new primitive founder while the corpse, archive and
descendants stay. The host records endings after the death's publication and
again for every founder corpse on recovery. The cellular server now refuses only
an unusable carried action, not the whole tick.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 07:26:33 -04:00

39 lines
2.2 KiB
Markdown

# M11.6: Commit permadeath and complete restart
A cellular life that dies stays dead, its corpse and history remain, and its
player starts again as a new primitive founder. The engineering contract is
[ADR-0127](../adr/0127-cellular-permadeath-and-restart.md). The client death and
restart flow is the maintainer's (client UI is deferred).
## Boundaries
Read ADR-0098, ADR-0100, ADR-0107, ADR-0124, ADR-0125 and ADR-0127. Recovery and
replay must never revive a life. A restart is an ordinary new life request; it
grants no carried-over biology, position or inventory.
## Segments
| Segment | Affected modules | Acceptance evidence |
|---|---|---|
| 11.6a: durable endings and restart | Schema v37, life reservation store, cellular host, server tick build | A starved founder's ending is recorded; the account has no active owner region; a new request is born with a new identity while the corpse remains; the first request still reports its birth; a request during a live life is refused; a restart recovers the same state; a stale action of a dead account refuses only itself |
| 11.6b: death and restart presentation | Engineering client (maintainer) | Death cause and restart are readable; no corpse retrieval or resurrection shortcut |
## Required checks
- Death versus mutation, bud and logout in the same tick; crash between the
publication and the ending record (recovery records it); an old session's action
after death; repeated lives of one account are independent.
- Linux CI PostgreSQL evidence before claiming the live path.
## Progress
- 2026-10-14: 11.6a implemented. Schema v37 adds `life_reservations.ended_commit`
(set once by a trigger-guarded transition), `one_active_life_per_account`, drops
the one-binding-per-account constraint, and updates the reservation, owner lookup
and birth publisher to consider only active lives; `end_cellular_lives` records
endings. The host records endings after the publication of a death and again for
every founder corpse on recovery. `serve_cellular` refuses only an unusable
action. `cellular_death_is_final_and_account_restarts` (PostgreSQL) covers the
acceptance evidence above except the stale-action path, which is server-loop
behaviour.