Files
aevolution/docs/PROJECT_VISION.md
T
dingoandClaude Opus 5 d5b4bd068e Initial commit: architecture docs and headless engineering proof
Aeternalis Evolution, a custom-engine persistent evolutionary MMO.

This first commit establishes the project skeleton:

- Architecture and design docs: project vision, system overview,
  engineering constitution, roadmap, 19 ADRs, and the simulation,
  world, network, persistence and infrastructure architectures.
- Headless engineering proof: deterministic synthetic particles,
  component lifecycle, explicit PRNG streams, canonical snapshots
  and restored execution.
- Build and tooling: CMake 3.28+ / Ninja presets, C++23 feature
  check, clang-format and clang-tidy config, format check script,
  Windows check script, and a Docker build context.
- Tests: unit tests, benchmarks, a snapshot fuzz target and CLI
  integration wiring.

No gameplay, renderer, network service or running deployment yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-14 15:44:41 -04:00

71 lines
5.6 KiB
Markdown

# Aeternalis Evolution
## Purpose and first product
The persistent protagonist is a planet's evolutionary history. Each player life
starts as a primitive cell, develops an ecological strategy, can seed autonomous
descendants, and ends permanently. 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 new life is a primitive cell with no account-age biological advantage. Historical knowledge may persist. |
| Persistent ancestry | Descendants are independent wildlife, survive the player's logout/death, and fail through ecological pressure. Extinct genomes remain in history. |
| 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
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.