# 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. ```sh 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](https://packages.ubuntu.com/noble/g%2B%2B-14), [LLVM packages](https://packages.ubuntu.com/clang), [checkout v4.2.2 commit](https://github.com/actions/checkout/commit/11bd71901bbe5b1630ceea73d27597364c9af683). Harbor, Argo CD, Argo Workflows and Kubernetes follow [infrastructure architecture](../docs/architecture/INFRASTRUCTURE_ARCHITECTURE.md) and [operations gates](../docs/infrastructure/OPERATIONS.md). World0 promotion is manual; state is protected from routine cleanup. No fake endpoints/credentials or unvalidated storage-class manifests are supplied.