# 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 20 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`. 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 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 | 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 | | 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 | | 5 | M2.1 energy/matter ledger | Agreed units/ranges, atomic transfers, nonnegative balances and conservation tests before organisms | | 6 | M2.2–2.6 first headless energy cycle | Explicit source → producer → consumer → death → decomposition → nutrients; seeded million-tick ledger 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.