dingoandClaude Opus 5 1c8b292147 Keep a distribution, because a mean cannot say who survives
M4.1 defines the tier 2 record and who may act on it, and nothing else: no
collapse transaction, no population advance, no materialization, no habitat
geometry. Those are M4.2 to M4.4 and each needs its own decision.

The named risk for this step is that population averages hide viable outliers,
which is a property of the record rather than of the maths applied to it later,
so it is answered here. Age classes each carry their own count and their own
reserve. A count with a mean reserve cannot tell a provisioned cohort from one
where half the members hold nothing, and nothing downstream can recover what
that discarded. Within a class members are indistinguishable; that is the
declared resolution and a stated loss. No accessor returns a mean, because an
average that is easy to reach becomes the authority.

Totals are summed from the classes rather than stored beside them, following the
archive's rule that a second tally is a thing that can disagree. Lineage is not a
field at all: ancestry is resolved from the genome through the archive, so a
cohort cannot contradict it or invent parentage from membership. Residuals are
integer numerators strictly below one member and are never added to a count.

Ownership is enforced rather than described. One record per habitat and genome
makes no-inventory-spendable-in-two-tiers unrepresentable instead of forbidden,
and replacement is refused under a different worker or an older epoch. That is a
single-process invariant; fencing between workers is M7 and M10. The
approximation bound is carried and never computed, since carrying a bound is not
meeting one.

All nine guards were confirmed load-bearing by removing each and rerunning. An
earlier sweep reporting none of them load-bearing was wrong and discarded: it
wrote to /tmp, which Git Bash and PowerShell resolve differently, so nothing was
ever mutated.

Release 34/34, analysis, ASan 34/34 and clang-format all ran and passed here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-24 06:14:07 -04:00

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

S
Description
No description provided
Readme
7.5 MiB
Languages
C++ 83.4%
PLpgSQL 9.1%
Shell 2.8%
JavaScript 1.5%
CMake 1.3%
Other 1.9%