Aeternalis Evolution, a custom-engine persistent evolutionary MMO. This first commit establishes the project skeleton: - Architecture and design docs: project vision, system overview, engineering constitution, roadmap, 19 ADRs, and the simulation, world, network, persistence and infrastructure architectures. - Headless engineering proof: deterministic synthetic particles, component lifecycle, explicit PRNG streams, canonical snapshots and restored execution. - Build and tooling: CMake 3.28+ / Ninja presets, C++23 feature check, clang-format and clang-tidy config, format check script, Windows check script, and a Docker build context. - Tests: unit tests, benchmarks, a snapshot fuzz target and CLI integration wiring. No gameplay, renderer, network service or running deployment yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Container and delivery foundation
M0 builds/tests evo-sim. It deploys no Kubernetes resources, publishes no image, connects no database and supplies no persistent region server.
docker build --file deploy/docker/Dockerfile --tag aeternalis-evo:dev .
docker run --rm --network none --read-only --cap-drop ALL \
--security-opt no-new-privileges aeternalis-evo:dev \
--seed 123456 --ticks 1000 --verify-replay
The GCC14 build stage runs CTest before producing the non-root UID/GID10001 runtime. It includes the executable and system runtime libraries. Builder package versions are recorded at /usr/share/evo/build-packages.txt. Output is stdout; file outputs require an explicitly mounted writable destination.
CI covers GCC14 Debug/Release, MSVC, LLVM19 format/tidy, ASan/UBSan, separate TSan, bounded seeded libFuzzer and image build/smoke. TSan validates its configuration on the current sequential kernel, not a future scheduler. Runtime/runner failures must be diagnosed, never marked passing. Retain useful fuzz reproducers and add longer campaigns when decoder complexity warrants them.
Scaffold limits: hosted runners, Ubuntu tag and distro security packages move. Before publishing, review/pass UBUNTU_IMAGE as an immutable digest, retain package manifests/results, produce an SBOM, scan/sign and promote the final digest through reviewed GitOps. The pinned checkout action also needs normal security updates. GCC14 package, LLVM packages, checkout v4.2.2 commit.
Harbor, Argo CD, Argo Workflows and Kubernetes follow infrastructure architecture and operations gates. World0 promotion is manual; state is protected from routine cleanup. No fake endpoints/credentials or unvalidated storage-class manifests are supplied.