Births validated each parent against the progressively modified candidate, so a child allocated earlier in the same batch was already active and could fund a further birth. Two generations could appear in one tick, which ADR-0028 forbids. The contract was already correct; the implementation did not enforce it. Fix parent eligibility on entry to the reproduction phase, after terminal facts and feeding, and check every intent before applying any birth. A rejected cascade leaves the whole tick unchanged, as before. The regression test admits one intent whose parent is created by the preceding intent and requires unborn_actor with balances, progress, receipts and slot states untouched. It fails against the unguarded implementation and passes with the guard. The same pair succeeds across two ticks and records the grandchild ancestry. Native Release, clang-tidy analysis, ASan and format checks were rerun and pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Aeternalis Evolution
A custom-engine persistent evolutionary MMO. The world retains its biological history; each player life begins as a primitive cell and ends permanently.
This repository starts with architecture and a headless engineering proof: deterministic synthetic particles, component lifecycle, explicit PRNG streams, canonical snapshots and restored execution. It contains no gameplay, renderer, network service. Dev verification manifests are separate from the simulation.
Start here
- Project vision and locked requirements
- System overview and module boundaries
- Engineering constitution
- Architecture decisions and proposals
- Actionable milestones 0–4 and later gates
- Open design questions
- Actual validation results
- Current delivery status and next steps
- Opt-in ECS evaluation and measurements
- Sequential command scheduling and recovery
- Local periodic spatial queries
- Energy/matter model and implemented ledger boundary
Read AGENTS.md before changing code. Architecture and contracts are authoritative over implementation. No external runtime library is needed for the initial proof. C++23 support is checked during configuration.
Build and run
Requires CMake 3.28+, Ninja and a C++23 compiler/standard library supporting
std::expected. GCC 14 is the initial Linux CI target; MSVC 19.44 or newer is
the Windows target. Detailed verified tool versions are in the validation report.
cmake --preset debug
cmake --build --preset debug
ctest --preset debug
./build/debug/evo-sim --seed 123456 --entities 8 --ticks 1000 --verify-replay
On Windows use a Visual Studio x64 developer shell, or the repository's
tools/windows-check.ps1 helper. Executables have .exe suffix on Windows.
./build/debug/evo-sim --seed 123456 --entities 8 --ticks 500 --save state.evo
./build/debug/evo-sim --load state.evo --ticks 500 --output results.json
The second command continues saved PRNG/component state. --verify-replay
compares an uninterrupted run to a midpoint serialization/restore run. JSON
reports the seed, ticks, active entities and canonical state hash. Snapshots
are bounded local test files; they are not crash-consistent production storage.
Checks and measurements
cmake --build --preset debug --target format-check
cmake --preset analysis
cmake --build --preset analysis
cmake --preset asan
cmake --build --preset asan
ctest --preset asan
cmake --preset release
cmake --build --preset release
ctest --preset release
./build/release/evo-benchmark
./build/release/evo-spatial-benchmark
ASan uses UBSan too on supported Linux compilers. TSan has a separate tsan
preset and is never combined with ASan. clang-format/tidy major 19 is the initial
analysis baseline. The optional Clang libFuzzer target exercises snapshot
restore. See testing strategy and
deployment scaffold for scope and commands.
Repository boundaries
include/evo exposes core values and the headless simulation API.
src/simulation implements component state, tick ordering and local snapshot
codec. src/accounting provides the independent finite-inventory ledger;
it is not yet part of particle snapshots. apps/evo-sim owns CLI/file I/O and reporting. tests holds contract,
fuzz and measurement programs. Future biology, world, networking and persistence
modules are documented boundaries; they are added when they have real behavior.
World0 is persistent state. No normal configure, build, test or CI job may create, reset, deploy to or delete it. Gitea builds the proof image for Harbor; a bounded dev verification Job and manual Argo templates are in deploy/. Persistent-world deployment still requires storage, ownership and backup gates.
The project license has not been selected. Do not infer an open-source license from a public dependency's license.