Files
aevolution/README.md
T
dingoandClaude Opus 5 89ad95bf12 Let a genome decide, and report where each axis actually acts
M3.6 joins the M3 pieces: strategy_for derives a StrategyConfig from the
metabolic budget, founders are pre-diverged variants admitted to the lineage
archive, and evo-sim --ensemble runs them over a resource and temperature grid
with every cell's seeds split in half and never merged. ADR-0029's driver is
untouched, so the M2.6 fingerprint still holds. Nothing mutates during an
episode, so NPC mutation stays open.

Three things measurement found, kept rather than smoothed over. The report
aggregates were default-initialized, leaving their scalar counters
indeterminate. The resource level never reaches strategy derivation at all, so
the header now says where each axis acts instead of claiming both shape a
strategy. And the resource axis is not monotonic: a sweep peaks near 8000
femtograms and falls away on both sides, because only one consumer may bite a
target per tick, so scarcity concentrates mass into individuals that reach the
threshold while abundance spreads the same income too thin. The test asserts
that an axis moves the outcome and never a direction; an earlier draft asserted
a direction that held at two cells and the sweep disproves.

Earning a birth at all required pinning the investment fraction to the schema
floor, since intake scales with surface and investment with mass. That is a
finding about the ADR-0031/0032 cost model, now the second priority in STATUS.

Release 33/33, analysis, ASan 33/33 and clang-format all ran and passed here;
no Clang or GCC compile happens on this host, so Linux CI is still the first
result for this increment.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-23 23:03:52 -04:00

5.9 KiB
Raw Blame History

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

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. 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.