# Aeternalis Evolution ## Purpose and first product The persistent protagonist is a planet's evolutionary history. A fresh player life starts as a primitive cell. At reproduction the player can remain the parent or continue as its newborn offspring through a permanent one-way control transfer; the relinquished parent continues as autonomous wildlife. Each organism's death remains permanent. Structural mutations are expressed in offspring rather than rebuilding the parent's existing body. The first product is a compelling persistent cellular MMO ecosystem. Multicellularity and a modifiable three-dimensional voxel planet follow only after that loop works. This document translates the founding brief; it does not supersede its locked requirements. See [the architecture](architecture/SYSTEM_OVERVIEW.md), [decision records](adr/README.md), and [roadmap](ROADMAP.md). ## Locked requirements | Pillar | Contract | |---|---| | Absolute permadeath | Dead organisms never resume. A fresh life after death starts as a primitive cell with no account-age advantage. Voluntary one-way succession into living newborn offspring at birth is distinct from a fresh life; no return to the NPC parent or fallback after the child's death. | | Persistent ancestry | At birth the player stays as the parent or continues as the child; the other organism is independent wildlife. A relinquished parent retains its established behavior and reproductive plan. Independent relatives survive player logout/death and face ordinary ecology. Extinct genomes remain in history. | | Structural inheritance | Body-plan changes of a single cell are expressed in offspring; retain the parent's existing anatomy separately from its heritable offspring plan. A multicellular organism, one body of many cells, expresses an accepted change as a whole, funded from its reserve (maintainer, 2026-10-23; ADR-0179). Capability and construction costs remain real. | | Player-origin biology | A world can start with geology and chemistry but no life. Every lineage must ultimately reference a player-influenced founder. Do not silently seed prebuilt wildlife. | | Ecological progression | No classes, mandatory intelligence endgame, linear mutation tree, or cell-to-human ladder. Mixed and unfamiliar strategies are valid. | | Biological costs | Traits change physical/developmental parameters. Energy, matter, nutrients and environmental constraints determine consequences. | | Offline fairness | An offline player organism cannot move, feed, reproduce, mutate, grow, or progress passively. Logout safety treatment is unresolved. NPC descendants continue independently. | | Shared presentation | Perceivable biological state follows the same rules for NPCs and players. No arbitrary player/NPC/level/ownership labels. Friend recognition is a separate design question. | | Scale separation | Cellular 2D and macroscopic 3D domains exchange ecology and conserved resources, not literal cross-scale collision physics. | | Custom engine | Modern C++, no Unity or Unreal. Simulation is graphics independent. Specialized dependencies require justification. | | Authority and durability | Clients submit intentions. Server owns outcomes. Disposable workers recover from durable state and uniquely fenced region ownership. No database writes per simulation tick. | | Sparse world | Deterministic procedural base plus persisted changes; sparse, adaptive voxel detail. No planet-sized dense voxel allocation. | | Delivery | Testable increments, documented decisions, explicit simulation versions, restore exercises and human promotion of World 0. No renderer in the foundation. | ## Recommendations versus experiments The maintainer clarified structural inheritance, birth-time control choice and NPC-parent continuity on 2026-10-19 in [ADR-0163](adr/0163-structural-inheritance-and-offspring-succession.md). These are accepted target-game requirements, not implemented M11 behavior. Historical exact-copy budding, in-life mutations and primitive restart rules remain explicit versioned implementation baselines until their replacement is qualified. RECOMMENDATION: one repository, one modular backend initially, independent region worker processes, PostgreSQL metadata/durability and S3-compatible payload storage behind adapters. Split deployments when scaling or failure isolation requires it. Kubernetes scheduling capacity must grow with added nodes. EXPERIMENT: the initial proof uses a 50 ms tick quantum, integer positions in a small periodic test domain, a bounded component store and a simple explicit PRNG. This is an engineering fixture, not a selected game movement, physics, ecology, world size or timing model. Its format is deliberately not World 0's storage format. ## Assumptions requiring validation - Linux x86-64 is the first dedicated-server target; Windows is a developer and eventual client target. Actual R730xd CPU, storage, network and Kubernetes versions have not been inspected. - Approximately 128 GB is physical RAM, not a promised simulation budget. Co-located storage/database failures are shared hardware failures. - Steam distribution comes later through an identity-provider boundary. - The founding brief is the product authority. Architectural recommendations may be revised by ADR; gameplay questions are not silently resolved by code. ## Principal risks and evidence needed | Risk | Why it threatens the vision | Mitigation / decision evidence | |---|---|---| | Unfun repeated cellular lives | Correct infrastructure cannot rescue the first product | Instrument controlled playtests at M11; measure session variety and causes of death | | Ecological collapse or monopoly | One strategy could erase meaningful choices | Seeded ensemble experiments, energetic budgets, diversity and extinction histories; no automatic despawning disguised as selection | | Resolution exploit | Entity/population conversion could manufacture resources or immortality | Conservation ledger, exclusive representation ownership, adversarial round-trip tests | | Lost or duplicated authority | Death/reproduction could reverse or duplicate after failure | Fencing epochs, durable outcome acknowledgments, idempotent recovery and handoff fault tests | | Upgrade changes physical laws | Persistent ecology can be destroyed by a valid software deployment | Clone, migrate, accelerate, compare, approve, then world-wide compatible upgrade | | Morphology/animation scope | Arbitrary bodies may be computationally or artistically infeasible | Isolated later R&D with exit criteria; no dependency from cellular milestones | | One-host loss | Kubernetes replicas do not survive a chassis failure together | Separate backup failure domain and verified restore; explicitly limited initial availability | | AI architectural drift | Implementation can accidentally invent game rules or bypass authority | Constitution → ADR → contract → tests → code review; small independently reviewable changes | All 38 founding open questions are tracked in [OPEN_QUESTIONS.md](architecture/OPEN_QUESTIONS.md), with owners and decision gates.