# Project status and next steps Updated 2026-09-19. The repository contains an engineering foundation and a deterministic headless proof. It does not yet contain cellular gameplay or a persistent simulation server. The founding vision remains unchanged. ## Completed implementation - Vision, architectural pillars, risks, open-question register, architecture diagrams, biological contracts, engineering constitution and 23 ADRs. Proposed/deferred choices remain distinct from accepted proof decisions. - M0–M4 task breakdowns with dependencies, acceptance evidence and risks, plus M5–M14 gates in [ROADMAP.md](ROADMAP.md). - C++23 CMake/Ninja library and CLI with no graphics, networking, database or Kubernetes dependency. Versioned fixed ticks, stable entity IDs, component lifecycle and explicit per-entity seeded randomness. - Bounded canonical snapshots and restore, plus replay verification. An independent reference fingerprint and Release-active tests cover lifecycle, malformed data, overflow, seeded properties and CLI save/load. - Formatter, static analysis, sanitizer presets, codec fuzz entry point, benchmark, structured host logging and metrics output. Benchmark compiler metadata now resets numeric formatting after printing its hexadecimal state hash. ## Delivery and verification Git remote is `https://git.aeternalisgames.com/dingo/AEvolution.git`. The maintainer added a working Gitea/Harbor workflow; run 1399 on `8ab48d3` successfully verified 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. That verified image was previously pinned. The maintainer's subsequent GitOps commit `20e609d` selects the run 1399 image at `sha256:0c6c6e1ac28de2ce0648fd0992ca694963e303ef5c9414fe5ac668937136800d`; the M1.6 change preserves that independent deployment choice. 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 confirms Argo is configured and deployment additions will sync when a pod workload is ready. This workspace has no kubeconfig, so completed dev Job execution is not independently verified. This is not a blocker for M1. The repository supplies a restricted dev Job and bootstrap examples; image publication does not demonstrate a Kubernetes rollout or world recovery. See [VALIDATION.md](engineering/VALIDATION.md) for actual commands/results and [deploy/README.md](../deploy/README.md) for image promotion and application setup. Local `INITIAL_BRIEF.md` and `OpenAI_ChatLog.md` are maintainer-provided untracked material and are not automatically included in commits. ## Next reviewable increments, in order M1.5 progress: the opt-in row/EnTT4 experiment now checks canonical equality, restore continuation, retired identities and allocator balance, and records seven-sample sparse/dense/churn results. Windows Release, analysis and ASan checks passed, as did Linux Release, analysis and ASan/UBSan in Gitea run 1404. All 56 sample fingerprints match across platforms. ADR-0005 retains rows for the bounded proof; the general production ECS remains a later measured choice. | Priority | Work | Completion evidence | |---|---|---| | 1 | M2.1 energy/matter ledger | Agreed units/ranges, atomic transfers, nonnegative balances and conservation tests before organisms | | 2 | M2.2–2.6 first headless energy cycle | Explicit source → producer → consumer → death → decomposition → nutrients; seeded million-tick ledger evidence | | Delivery gate | Add/update the dev workload when a deployable increment needs it; Argo is ready | Observe Job/pod completion separately from image publication; no World0 changes | M1.6 now implements [the sequential scheduler contract](architecture/SCHEDULER_CONTRACT.md): exact-tick admission, bounded ordered lifecycle commands, receipts and atomic rollback on rejection. Windows Release, clang-tidy, ASan and formatting checks pass. Permutations across 32 seeds, restored continuation, duplicate/late/future inputs, limits and exhaustion are covered. The no-input golden and snapshot v1 are unchanged. Gitea run 1407 passed all Linux checks, ECS, TSan and image jobs; evidence is recorded in the validation report. Nonempty batches copy world state; this favors a clear transaction boundary for the proof, not a measured realtime performance claim. No thread pool or gameplay input protocol is introduced. M1.7 implements read-only periodic neighborhood queries with stable IDs and inclusive integer-distance boundaries. A nine-image oracle checks 2,304 seeded queries across initial, scheduled and restored worlds. Boundary and full-capacity tests supplement the oracle. The benchmark records uniform/clustered worlds up to 100,000 entities. This is a linear correctness baseline, not a production spatial index. See the spatial contract and validation report for scope/evidence. Before biology, resolve the relevant heredity and energetic contracts rather than treating proof particles as organisms. Exact game tick rate, NPC mutation, logout treatment, species/extinction rules and multicellular transition remain open decisions. Renderer/networking remain later milestones. Deployment availability does not complete M7/M8: fenced ownership, durable outcomes, backup restore and world-version migration require their own implementation/fault tests.