Close the M2.5 fixture cycle. A bounded list of trusted reproduction intents runs after feeding and before decomposition, so a consumer can fund offspring from what it ingested and a process terminated in that tick cannot reproduce. The intent names a withdrawal from the parent reservoir; a fixed construction fraction endows the child and the remainder becomes real heat and waste. Nothing is credited from outside the community, so conserved totals are unchanged by a birth. Reserved slots are pre-allocated at creation, so a birth never grows the ledger and a full community rejects rather than funding a smaller child. Slots never return to the unborn state, so process identities are never reused, and a parent reference plus origin tick outlive both organisms and survive decomposition. A child duplicates the configuration of its parent because no genome exists yet; this is duplication, not heredity. Default zero capacity leaves the M2.4 reservoir layout and every existing result unchanged, including golden d61ad5bf0c928c76. Native Release, clang-tidy analysis, ASan and format checks pass; Linux CI has not run for this increment yet. This defines no reproductive strategy, fecundity rule, mutation model, gestation, spatial placement or account ownership. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
150 lines
9.5 KiB
Markdown
150 lines
9.5 KiB
Markdown
# Project status and next steps
|
||
|
||
Updated 2026-09-21. 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 28 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.6 headless energy-cycle fixture | Complete capture/feeding/reproduction/decomposition cycle, seeded million-tick ecosystem runs and diagnostics |
|
||
| 2 | M3.1 immutable genome schema and ancestry | Versioned developmental capability data replacing M2.5's duplicated configuration |
|
||
| 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.
|
||
Native Release/ASan/analysis/format checks passed, as did all jobs in Gitea run
|
||
1409. All 72 Linux benchmark result checksums and match counts equal Windows.
|
||
|
||
M2.1 adds an independent finite-inventory accounting library (ADR-0024). Typed
|
||
picojoules and C/N/P/other femtograms transfer atomically across bounded local
|
||
reservoirs. Opening totals are checked, repeated action IDs rejected, and failures
|
||
leave both balances and action watermark unchanged. One million seeded transfers
|
||
are checked against independently maintained balances and recomputed totals.
|
||
No organisms, biochemical rates, external replenishment, world snapshot format
|
||
or deployment changes are included. Conservation does not establish valid
|
||
chemistry or reusable heat; process restrictions are M2.2 work.
|
||
Native Release, clang-tidy, ASan and formatting passed; Gitea run 1411 passed all
|
||
Linux checks, ECS, TSan and image publication. Validation details are recorded
|
||
in the engineering validation report.
|
||
|
||
M2.2 implements a synthetic finite-source producer process owning its ledger.
|
||
It captures energy, sends conversion losses to heat, and funds whole material
|
||
recipes from reserves and finite nutrients. Fractional rates and efficiency
|
||
carry exact remainders; tick/remainders and balances commit together. Tests cover
|
||
hand-calculated outcomes, 32 seeded reference/replay runs, source and nutrient
|
||
exhaustion, invalid tick/config rejection and u64 arithmetic limits. No organism,
|
||
genome, database, process snapshot or deployment is implied by this fixture.
|
||
Native Release, analysis, ASan and format checks passed, and Gitea run 1413
|
||
passed all Linux checks, ECS, TSan and image jobs.
|
||
|
||
M2.3 adds a shared feeding community with one producer and up to 16 consumer
|
||
capabilities. One ledger owns all process resources, heat and waste. Ordered
|
||
intake-capped feeding, producer progression and terminal depletion commit as one
|
||
tick; a rejected request leaves the entire community unchanged. Tests cover
|
||
predation, resource contention, terminal actors, batch order/replay and conservation.
|
||
No spatial/perception validation,
|
||
organism biology, persistent checkpoint or deployment is included in this fixture.
|
||
Native Release, analysis, ASan and formatting passed; all four Gitea run 1415
|
||
jobs passed.
|
||
|
||
M2.4 adds terminal events with preserved corpse inventory, followed by a shared
|
||
bounded decomposition phase. Energy moves to heat, elemental matter returns to
|
||
nutrients, and next-tick producer growth can use those nutrients. Corpses retain
|
||
their process ID and cannot resume activity. Invalid ticks roll back death and
|
||
decomposition with all earlier phases. Default zero decay preserves earlier
|
||
fixture behavior. This is not death-cause biology, microbial chemistry, corpse
|
||
scavenging, persistent lineage history or a database-backed world.
|
||
Native Release, analysis, ASan and formatting passed, and all four jobs in Gitea
|
||
run 1417 passed.
|
||
|
||
M2.5 adds funded budding (ADR-0028). A bounded list of trusted reproduction
|
||
intents runs after feeding and before decomposition, so a consumer can fund
|
||
offspring from what it ingested and a process terminated in that tick cannot
|
||
reproduce. The intent names a withdrawal from the parent; a fixed construction
|
||
fraction endows the child and the remainder becomes real heat and waste. Reserved
|
||
slots are pre-allocated at creation, so a birth never grows the ledger and a full
|
||
community rejects rather than funding a smaller child. Process identities are
|
||
never reused and a parent reference plus origin tick outlive both organisms.
|
||
A child duplicates its parent's configuration because no genome exists yet; this
|
||
is duplication, not heredity. Default zero capacity leaves every M2.4 result and
|
||
the particle goldens unchanged. Native Release, analysis, ASan and formatting
|
||
passed; Linux CI for this increment has not run yet. This is not a reproductive
|
||
strategy, fecundity rule, mutation model or funded founder admission.
|
||
|
||
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.
|