Close the M2.5 fixture cycle. A bounded list of trusted reproduction intents runs after feeding and before decomposition, so a consumer can fund offspring from what it ingested and a process terminated in that tick cannot reproduce. The intent names a withdrawal from the parent reservoir; a fixed construction fraction endows the child and the remainder becomes real heat and waste. Nothing is credited from outside the community, so conserved totals are unchanged by a birth. Reserved slots are pre-allocated at creation, so a birth never grows the ledger and a full community rejects rather than funding a smaller child. Slots never return to the unborn state, so process identities are never reused, and a parent reference plus origin tick outlive both organisms and survive decomposition. A child duplicates the configuration of its parent because no genome exists yet; this is duplication, not heredity. Default zero capacity leaves the M2.4 reservoir layout and every existing result unchanged, including golden d61ad5bf0c928c76. Native Release, clang-tidy analysis, ASan and format checks pass; Linux CI has not run for this increment yet. This defines no reproductive strategy, fecundity rule, mutation model, gestation, spatial placement or account ownership. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5.1 KiB
Reproduction, life ownership and permadeath
Locked: irreversible death, independent descendants and no offline progression. Strategy/heredity/logout fairness are proposals requiring explicit acceptance before gameplay. Separate account, controlled organism, genome and lineage IDs. Historical creator references grant neither wildlife ownership nor visual labels.
flowchart TD
A[Account] -->|current control grant| P[Living organism]
A --> H[History without biological bonuses]
P -->|funded reproduction| D[Independent wildlife descendants]
P -->|permanent death| X[Historical dead organism]
X --> H
A -->|new life| N[Primitive founder]
No resurrection, retained power, checkpoint or special corpse-retrieval mechanic. Corpse biomass follows ordinary ecology, not an account recovery entitlement.
Reproduction and death contracts
Proposed intention: Reproduce(action_id, parent_id, expected_revision, strategy, candidate_id?). Server resolves life/control state, prerequisites, costs,
environment, offspring allocation and genomic change. Client supplies no
authoritative child genome/count/cost. Parent costs, ancestry/genome records,
offspring inventory/allocation and event form one recoverable logical operation.
Durable acknowledgment requires recoverability; duplicate IDs return prior outcome.
Binary fission proposes one autonomous descendant, with parent continuity/control and splitting still open. Eggs/live birth use bounded young or cohorts with explicit investment/gestation/mortality. Broadcast/spores use funded statistical cohorts; theoretical fecundity never requests unbounded AI allocation. Capacity backpressures, rejects or aggregates; it cannot grant free offspring or silently delete committed lineages. NPC mutation/heredity/juvenile viability remain open.
Alive→Dead is terminal for the organism ID. Remove actions before later phases; transfer inventory to corpse/detritus exactly once. Proposed ordering resolves lethal damage/maintenance before reproduction; changing this needs a decision and fixtures. Descendants receive no arbitrary mortality modifier because a player died: inherited demands/tolerances interact with ecology independently.
Committed death must survive snapshot replay before recovered state is exposed. Unavailable durability withholds final outcome acknowledgment and quarantines pending irreversible changes. A new life follows the same primitive founder rule for every account, with initial matter/energy provenance. No growth/reserve or capability bonus transfers from history.
Offline experiment: suspended inventory
Propose durable suspension outside progressing tiers. Freeze position reference, genome, age/growth, energy/matter, disease, gestation and every biological timer. Inventory stays in global accounting but cannot interact. Wildlife continues.
stateDiagram-v2
Active --> SuspendPending: logout or detected disconnect / freeze
SuspendPending --> Suspended: durable ownership transfer
Suspended --> Active: validated unique resume grant
Active --> Dead: committed death
SuspendPending --> Dead: lethal outcome determined before freeze
SuspendPending already has no biological advancement at the authoritative freeze boundary. Servers can react only to detectable disconnects; heartbeat/detection bounds need a logout ADR. Clients cannot backdate freeze time. Resume performs no elapsed-time biology and first replays committed death. Changed habitat, blocked spawn, duplicate login and danger need a policy without free travel/duplication.
Suspension may evade predation or hoard biomass. A combat delay that advances offline biology violates the brief. Evaluate in-session eligibility/admission restrictions without progressing suspended organisms. Indefinite retention and matter disposition also remain open; no proposal is shipped as a settled rule.
Tests: dead IDs never act/resume; death/corpse exactly once; reproduction balanced and atomic despite insufficient nutrients with abundant energy; retries stable; descendants independent of parent death/logout; arbitrarily long suspension preserves every timer; same-tick death/reproduction ordering; huge spore requests; all suspend/resume crash points; changed habitat; unique control grants and death committed after snapshot. Extinction includes suspended viability.
Implemented M2.5 fixture boundary
ADR-0028 implements funded budding inside the synthetic feeding community only. The parent survives and pays an explicit investment; construction overhead goes to heat and waste; a bounded pre-allocated slot capacity rejects rather than granting free or reduced offspring. Ancestry is a parent reference and an origin tick that survive both deaths.
This settles none of the contracts above. Binary fission continuity, eggs, cohorts, broadcast spores, gestation, strategy selection, mutation candidates, client intentions, control grants, durable acknowledgment and logout treatment remain open. The fixture has no accounts, so a parent reference grants no ownership and no label. Test processes are not wildlife and do not seed a persistent world.