From 1c6e6e119a5b3f9dad971c82219b1c219b506878 Mon Sep 17 00:00:00 2001 From: dingo Date: Sat, 19 Sep 2026 09:29:10 -0400 Subject: [PATCH] Pin verified dev image and document completed foundation checks --- README.md | 2 +- deploy/README.md | 11 ++++++--- deploy/kubernetes/dev/kustomization.yaml | 3 ++- docs/STATUS.md | 10 +++++++- docs/engineering/VALIDATION.md | 31 ++++++++++++++++++++---- 5 files changed, 46 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 936c31b..786a00c 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ 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 or running Kubernetes deployment. +network service. Dev verification manifests are separate from the simulation. ## Start here diff --git a/deploy/README.md b/deploy/README.md index 90178eb..25a7f9a 100644 --- a/deploy/README.md +++ b/deploy/README.md @@ -6,6 +6,11 @@ successfully built, tested and published commit `8ab48d3`. This repository adds broader checks and a bounded **stateless proof Job**. It is not a region server. Cluster execution must be recorded separately from image publication. +The expanded [run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402) +passed all checks and published `4c2cc04`. The dev Kustomize manifest already pins +that verified image digest. Argo bootstrap examples still need the actual +application namespace and destination; do not apply examples unchanged. + ## Gitea and Harbor The single workflow is `.gitea/workflows/build.yaml`. The existing runner label @@ -75,9 +80,9 @@ credential. The project allows only Job, ServiceAccount and NetworkPolicy there. Before syncing: 1. Wait for successful checks and publication of the intended commit. -2. Replace the digest marker in `deploy/kubernetes/dev/kustomization.yaml` with - the published `sha256:<64 hex>` digest, review and commit it. The marker is - intentionally invalid and cannot launch an accidental fallback image. +2. Update `deploy/kubernetes/dev/kustomization.yaml` to the published + `sha256:<64 hex>` digest, review and commit it. It currently pins run 1402; + no floating tag or fallback image is used. 3. Run `kubectl kustomize deploy/kubernetes/dev`. Check exactly three resources, all in evolution-dev, the selected digest and no unresolved marker. 4. Full-sync the dev app. Selective sync skips hooks. diff --git a/deploy/kubernetes/dev/kustomization.yaml b/deploy/kubernetes/dev/kustomization.yaml index a27dfbe..22e252b 100644 --- a/deploy/kubernetes/dev/kustomization.yaml +++ b/deploy/kubernetes/dev/kustomization.yaml @@ -8,4 +8,5 @@ resources: images: - name: evo-sim newName: registry.aeternalisgames.com/aeternalis/aevolution - digest: sha256:REPLACE_WITH_PUBLISHED_64_HEX_DIGEST + # Gitea run 1402; source commit 4c2cc04ac47d37c6191a9ef02d4bbba716a930dc. + digest: sha256:8fce2b462c9907f38d3fb832afeb70d0bff068dd832b2171e861186dbcb8e6b9 diff --git a/docs/STATUS.md b/docs/STATUS.md index afd50bc..43de929 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -29,6 +29,14 @@ and published. The foundation update extends that single workflow with Linux analysis/sanitizers/fuzzing and runtime smoke verification. Images target `registry.aeternalisgames.com/aeternalis/aevolution`. +[Run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402) +passed all jobs for source commit `4c2cc04`: Linux checks, separate TSan and image +smoke/publish. The dev manifest now pins the published image at +`sha256:8fce2b462c9907f38d3fb832afeb70d0bff068dd832b2171e861186dbcb8e6b9`. +Windows checks also pass; full commands and intermediate CI failures are recorded +in the validation report. M0's engineering proof is verified; dev cluster +execution is the remaining delivery check, not a claim of persistent-world readiness. + The maintainer reports Argo is configured. This workspace has no kubeconfig; the app/source mapping and completed dev Job are not yet independently verified. The repository supplies a restricted dev Job and bootstrap examples; image @@ -43,7 +51,7 @@ material and are not automatically included in commits. | Priority | Work | Completion evidence | |---|---|---| -| 1 | Close M0 delivery: run expanded Gitea checks, select a successful image digest and verify the existing dev Argo mapping | Green checks, digest recorded, dev Job Complete with replay_verified=true; no World0 changes | +| 1 | Verify the existing dev Argo mapping and sync the pinned, validated image | Dev Job Complete with replay_verified=true; no World0 changes | | 2 | M1.5 ECS evaluation: compare the bounded store with a pinned mature ECS in an isolated benchmark using sparse biological capability workloads | Iteration/lifecycle/memory/serialization measurements, license review and updated ADR-0005; no automatic adoption | | 3 | M1.6 scheduler/input contract: ratify phase order and command admission before implementing a sequential scheduler | Stable input order, one writer, deterministic merges and replay equivalence | | 4 | M1.7 local spatial contract | Neighborhood queries checked against brute force, wrap/boundary/unit tests and measured workload | diff --git a/docs/engineering/VALIDATION.md b/docs/engineering/VALIDATION.md index 63efaaa..e000ef8 100644 --- a/docs/engineering/VALIDATION.md +++ b/docs/engineering/VALIDATION.md @@ -1,6 +1,7 @@ # Validation report -Recorded 2026-09-19. Native checks apply to base commit `8ab48d3` plus the +Recorded 2026-09-19. Latest verified Linux delivery: **run 1402 passed** on +`4c2cc04ac47d37c6191a9ef02d4bbba716a930dc`. Native checks apply to base commit `8ab48d3` plus the foundation-delivery working changes committed with this report. Simulation rules and snapshot format remain version 1; the only C++ change is benchmark metadata. Results below distinguish executed checks from pending Linux/cluster gates. @@ -24,7 +25,7 @@ Results below distinguish executed checks from pending Linux/cluster gates. | `./build/release/evo-sim --seed 123456 --entities 8 --ticks 1000000 --verify-replay` | Exit 0; replay_verified=true; hash fab22c2e8ae1c379 | | `./build/release/evo-benchmark` | Exit 0; MSVC 1944 Release, seed 123456, 10000 entities, 1000 ticks, 0.0210666 seconds, hash 3bad6db1612cbd1 | | Git Bash `bash -n tools/ci/linux-check.sh` and `bash -n tools/ci/publish-image.sh` | Syntax checks passed; no Linux execution implied | -| `kubectl kustomize deploy/kubernetes/dev` | Rendered Job, ServiceAccount and NetworkPolicy in evolution-dev; image marker intentionally unresolved | +| `kubectl kustomize deploy/kubernetes/dev` | Rendered Job, ServiceAccount and NetworkPolicy in evolution-dev; final render pins the verified run-1402 image | CTest covers the independently frozen 1000-tick fingerprint d61ad5bf0c928c76, seeded replay properties, malformed/semantic snapshot rejection, entity lifecycle, @@ -42,15 +43,15 @@ on `8ab48d3a5639121693f5881b600482e870b49f05` completed successfully. API job re confirm verify (configure/build/CTest) and publish (Docker build/push) succeeded on runner theraborn-runners-runner-0, label ubuntu-22.04. This is evidence for the original workflow, not the expanded sanitizer/analysis jobs added in this change. -Exact Linux tool versions must come from the expanded job logs; a runner label +Exact Linux tool versions and expanded-run results appear below; a runner label is not a compiler version. ## Limitations and next gates - Local Docker Desktop has no running Linux engine. Container checks must run on the configured Gitea runner; no local container success is claimed. -- Expanded Linux GCC14/Clang19, ASan/UBSan, TSan and libFuzzer jobs are pending a - pushed workflow run. A configured job is not a passing check. +- Expanded Linux GCC14/Clang19, ASan/UBSan, TSan and libFuzzer evidence is recorded + below. TSan currently validates a sequential kernel, not future concurrency. - Sandbox process restrictions stalled native Ninja and blocked Git Bash signal pipes. Those attempts were stopped; checks reran successfully outside sandbox. - Repeated VsDevCmd initialization grew PATH beyond cmd's limit. The helper now @@ -78,3 +79,23 @@ personality(ADDR_NO_RANDOMIZE) inside the Docker build sandbox. The image job wa skipped, as required. This is not recorded as a TSan pass. The follow-up isolates execution in a container with the narrowly constrained profile from ADR-0020; its result must be recorded after execution. + +## Successful delivery run 1402 + +[Run 1402](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/1402), +commit 4c2cc04ac47d37c6191a9ef02d4bbba716a930dc: every job succeeded. The general +checks reused Docker's valid cache for unchanged checked sources; their full +execution also passed in run 1401. TSan executed all five CTests successfully in +2.71 seconds using the scoped profile and writable tmpfs outputs. Run 1401 had +first exposed a non-root tmpfs permission error; setting explicit mode=1777 on +these isolated scratch mounts fixed it. No test was disabled or ignored. + +The runtime image built, ran the restricted replay smoke test and was pushed to: + +`registry.aeternalisgames.com/aeternalis/aevolution:sha-4c2cc04ac47d37c6191a9ef02d4bbba716a930dc-run-6-1` + +Registry digest: +`sha256:8fce2b462c9907f38d3fb832afeb70d0bff068dd832b2171e861186dbcb8e6b9`. + +The dev manifest pins this digest. This proves build/test/image delivery; Argo +application mapping and Kubernetes Job completion remain unverified locally.