The two runs allocated contested breeding slots in different orders: the individual run by member insertion order, the aggregate run by stored class order, which is youngest first. When eligible parents outnumber free slots that decides which parents reproduce, for a reason that has nothing to do with averaging. The control never reached the capacity boundary and so could not see it, which left ADR-0040's central claim unsupported rather than merely imprecise. The allocation order is part of the stated rule now, oldest first, honoured at both resolutions: classes partition ages, so the oldest class holds the oldest members, and ordering inside a class stays something only the individual run can see, which is a resolution effect rather than an implementation difference. A second control sits at the capacity boundary, twelve eligible parents contending for one free slot, and both controls compare the whole distribution of members rather than censuses. That change matters by itself: whoever breeds hands the same investment to a child either way, so every total agrees while the distribution does not, and a census-only control cannot see a different parent having bred. The probe diverging only by tick 44 is that effect. Attribution was verified by mutation rather than argued. Restoring the individual run's insertion order fails the new control; restoring the aggregate run's youngest-first order fails it; the earlier one-unit drift in aggregate upkeep still fails the first. Since either allocation order alone fails, the reported divergence is attributable to averaging. My first attempt at the control was wrong and the same sweep caught it. I gave the contested fixture ages descending with the index, reasoning that this made insertion order differ from age order; it does the opposite, and the individual-side mutation passed. Ages ascend now, so oldest-first disagrees with both the insertion order and the stored class order. Without the sweep the new control would have looked like it established attribution while covering half of it. Also added the depletion check the ADR's attribution argument relies on: a shared store that ran out would make intake order-dependent too. I had written that the fixture asserts this before it did, which is now true. The measurements were regenerated and are unchanged. Saying so plainly rather than as confirmation: the finding was about what the numbers can be attributed to, not about their values. Release 38/38, analysis, ASan 38/38 and clang-format all ran and passed here. 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
- Genome model and implemented v1 record
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
./build/release/evo-sim --ecosystem --seed 0 --episodes 3000
Ecosystem mode measures seeded bounded episodes of the synthetic feeding community and reports ticks, births, both mortality paths, extinctions and a fingerprint. It shares no state, snapshot or particle metric with the proof run, and its strategy constants are measurement inputs rather than simulation rules. See ADR-0029 for scope.
./build/release/evo-sim --ensemble --seed 0 --seeds-per-cell 4 --strategies 3 --tick-limit 400
Ensemble mode derives strategies from genomes instead of writing them, then runs
them on that same driver over a resource and temperature gradient. Each cell's
seeds are split in half and both halves are reported separately and never merged,
so a difference that appears in one half only is visible as the seed artifact it
is. Options belong to exactly one mode: --episodes counts episodes and is
rejected here, --seeds-per-cell counts seeds and is rejected in ecosystem mode.
A cell's numbers are not fitness, adaptation or balance, and the resource axis is
deliberately not monotonic. Lifetimes are censored: an organism still alive when
an episode stops is reported as a survivor with the time it was watched, never as
a death, so lived_ticks and observed_ticks answer different questions. See
ADR-0035 for scope and for why.
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. src/processes holds the synthetic
producer, feeding, reproduction and episode fixtures built on that ledger; they
are bounded experiments, not organism biology. src/biology holds the immutable
genome record, the deterministic development that derives a phenotype from it and
the metabolic budgets that give capability a cost, and the seeded mutation
catalog that proposes successors and the archive that keeps them. No fixture reads
a genome yet.
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.