dingoandClaude Opus 5 3f86dada0e Derive a phenotype from the genome without touching it
M3.2 adds derive_phenotype and plan_development as pure integer
functions of a genome, a growth state and an environment. Nothing is
stored: a phenotype is recomputed from retained inputs rather than
cached, so a cached copy can always be checked against a recomputation.

The risk this increment was scoped against is confusing the genome with
runtime damage. Growth and damage live in a separate state that no
function may write back, and no entry point takes a mutable genome.
Damage changes the phenotype and leaves the encoded bytes and content
digest identical, so heredity cannot carry acquired condition.

The genome's development version selects a rule set, which is what makes
that field worth carrying; an unknown version fails closed rather than
deriving under the wrong rules. Version 1 declares every constant. The
shape model is explicit rather than implied: the body is a cube of
uniform declared density, so extent is an exact integer cube root and
surface is six extents squared. Membrane mass follows surface and the
genome's thickness, maintenance follows total mass plus a membrane
upkeep term, and uptake scales with surface, so size trades uptake
against maintenance. A capability the genome does not carry yields zero.

A plan advances growth by at most the rule step, reduced to the largest
step the available material funds exactly, never a partial one and never
a grant. It reserves nothing and pays for nothing: the matching transfer
does not exist until M3.3, and an apply that moved no inventory would
look like a committed operation while conserving nothing.

The fixture genome is an exact 20 micrometre cube, so every derived value
is asserted as a hand-calculated literal, as are the half-built, damaged,
maximum and cube-root-boundary cases. Determinism is checked over 45
growth and temperature combinations. The declared flooring is pinned
rather than hidden: a body whose mass floors to zero advances its counter
for no material, granting no structure because none exists either way.

Omitted physics is a documented model limitation, not a modifier. Nothing
here is balance, and no organism yet develops. Native Release, clang-tidy
analysis, ASan and format checks pass 18/18; every existing golden and
fingerprint is unchanged. Linux CI has not run yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-22 21:48:24 -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.

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 and the deterministic development that derives a phenotype from it; nothing reads either 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%