M4.1 defines the tier 2 record and who may act on it, and nothing else: no collapse transaction, no population advance, no materialization, no habitat geometry. Those are M4.2 to M4.4 and each needs its own decision. The named risk for this step is that population averages hide viable outliers, which is a property of the record rather than of the maths applied to it later, so it is answered here. Age classes each carry their own count and their own reserve. A count with a mean reserve cannot tell a provisioned cohort from one where half the members hold nothing, and nothing downstream can recover what that discarded. Within a class members are indistinguishable; that is the declared resolution and a stated loss. No accessor returns a mean, because an average that is easy to reach becomes the authority. Totals are summed from the classes rather than stored beside them, following the archive's rule that a second tally is a thing that can disagree. Lineage is not a field at all: ancestry is resolved from the genome through the archive, so a cohort cannot contradict it or invent parentage from membership. Residuals are integer numerators strictly below one member and are never added to a count. Ownership is enforced rather than described. One record per habitat and genome makes no-inventory-spendable-in-two-tiers unrepresentable instead of forbidden, and replacement is refused under a different worker or an older epoch. That is a single-process invariant; fencing between workers is M7 and M10. The approximation bound is carried and never computed, since carrying a bound is not meeting one. All nine guards were confirmed load-bearing by removing each and rerunning. An earlier sweep reporting none of them load-bearing was wrong and discarded: it wrote to /tmp, which Git Bash and PowerShell resolve differently, so nothing was ever mutated. Release 34/34, analysis, ASan 34/34 and clang-format all ran and passed here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
322 lines
22 KiB
Markdown
322 lines
22 KiB
Markdown
# Project status and next steps
|
||
|
||
Updated 2026-09-23. 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 36 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 | M4.2 collapse active individuals | Transfer IDs and reserves into one cohort atomically, with exact ledger conservation |
|
||
| 2 | Revisit the ADR-0031/0032 reproduction cost model | Reproduction is affordable only at the genome schema's floor; decide whether that is intended before M4 builds cohorts on it |
|
||
| 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. Parent eligibility is fixed on entry to the phase, so a child born in
|
||
a tick cannot itself be a parent until the next one. 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.
|
||
|
||
M2.6 closes M2 with a deterministic ecosystem driver (ADR-0029). It owns one
|
||
community and one seeded stream, holds no inventory and emits only the intents
|
||
the earlier increments already accept, so no simulation contract changed. Two
|
||
limits shaped it: retained identities and capped slots mean one community is not
|
||
a population, and with no maintenance cost an uneaten consumer never dies. The
|
||
harness therefore measures many bounded episodes, with mortality from predation
|
||
and a configured lifespan delivered as a host terminal fact. The driver probes a
|
||
discarded copy each tick so it never submits a batch the community rejects; a
|
||
rejected tick is reported as a driver defect rather than absorbed as ecology.
|
||
`evo-sim --ecosystem` reports seeded episode ensembles: 3,000 episodes advanced
|
||
1,093,007 ticks, all reaching extinction, with deaths reconciling exactly against
|
||
founders plus births and conserved totals identical at every tick. That
|
||
demonstrates arithmetic and turnover, not ecological plausibility; strategy
|
||
constants are chosen inputs and must not become gameplay by having been measured.
|
||
Native Release, analysis, ASan and formatting passed; Linux CI has not run yet.
|
||
|
||
M3.1 opens M3 with the immutable genome record (ADR-0030) in a new `evo::biology`
|
||
library that nothing else links yet. A genome is validated once at construction
|
||
and exposes no mutator, so an invalid one cannot exist at runtime; `decode`
|
||
applies identical checks, so a decoded record is never less validated than a
|
||
constructed one. Schema 1 fixes the seven v0.1 capability kinds with units,
|
||
inclusive ranges, required flags and mandated developmental edges as schema facts
|
||
rather than record data. Identity is a nonzero world-scoped genome ID distinct
|
||
from every runtime identity, a nonzero origin event and zero or one parent, with
|
||
room reserved for recombination. The encoding is canonical, bounded and exact:
|
||
strict ascending order, a stored digest that is recomputed on decode, and a
|
||
trailing checksum, with the byte layout in schemas/genome-v1.md. No genome
|
||
affects any simulation; the M2 fixtures still duplicate founder strategies.
|
||
Development, phenotype, mutation and heredity remain M3.2 to M3.5. Native
|
||
Release, analysis, ASan and formatting passed; Linux CI has not run yet.
|
||
|
||
M3.2 derives a phenotype from that record (ADR-0031). `derive_phenotype` and
|
||
`plan_development` are pure integer functions of genome, growth and environment,
|
||
so a phenotype is recomputed from retained inputs rather than cached. Growth and
|
||
damage are runtime state that never reach the genome: damage changes the
|
||
phenotype and leaves the content digest identical, which is the risk this
|
||
increment was scoped against. The genome's development version selects a rule
|
||
set and an unknown version fails closed. Version 1 declares every constant:
|
||
the body is a cube of uniform declared density, membrane mass follows surface and
|
||
thickness, maintenance follows mass plus a membrane upkeep term, and uptake scales
|
||
with surface, so size trades uptake against maintenance. A capability the genome
|
||
does not carry yields zero. A plan advances growth by at most the rule step,
|
||
reduced to the largest step the available material funds exactly, and reserves
|
||
nothing: no inventory moves until M3.3. Omitted physics is a documented model
|
||
limitation, not a modifier, and the constants must not become tuning by having
|
||
been written down. Native Release, analysis, ASan and formatting passed 18/18;
|
||
Linux CI has not run yet.
|
||
|
||
M3.3 gives capability a cost (ADR-0032). `metabolic_budget` returns body
|
||
composition, maintenance, movement, construction, the per-tick intake limit and
|
||
the reproduction investment, in accounting types; `metabolism` is the single
|
||
translation layer and the genome record stays free of those types. Each budget
|
||
comes from a different phenotype quantity, so one parameter moves some and not
|
||
others: a thicker membrane costs more matter to build, more energy to hold and
|
||
more to haul, while leaving uptake, speed and assimilation identical. That
|
||
non-uniformity is asserted directly, because a capability that became a flat
|
||
multiplier is the failure this increment was scoped against. Composition is
|
||
declared per compartment, and splits give the remainder to the last channel so
|
||
parts sum back to the whole and a derived body can be spent without a rounding
|
||
leak. `processes::consumer_for` is the first path from a genome into the M2
|
||
fixtures, with opening inventory left to the caller so no matter is invented; a
|
||
derived consumer is shown driving a real feeding tick with the ledger conserving.
|
||
No existing fixture reads genomes yet and no organism spends any budget. Native
|
||
Release, analysis, ASan and formatting passed 19/19; Linux CI has not run yet.
|
||
|
||
M3.4 proposes successors (ADR-0033). A static catalog of four effects over the
|
||
seven capabilities is filtered by the M3.1 validation itself, so eligibility is
|
||
not a second rulebook: shedding a capability another declares as a prerequisite
|
||
fails without a rule written for it. Candidates are drawn without replacement by
|
||
rejection sampling on an explicit stream, so every eligible operator is exactly as
|
||
likely as any other, and the result is returned in canonical order with no score
|
||
anywhere in the record. The draw reads only the parent digest and a recorded
|
||
context, so the same context always returns the same candidates and a retry cannot
|
||
reroll, while a new event index earns a new draw. Selection regenerates the offer
|
||
and refuses a changed context outright rather than answering it with a different
|
||
mutation. A candidate reports what ADR-0032 would charge its successor and
|
||
reserves nothing. The uniformity test was confirmed to fail against a draw that
|
||
took the first eligible operators. Candidate count, mutation cost as a game rule,
|
||
inherited versus acquired expression, NPC mutation and recombination stay open;
|
||
no organism mutates. Native Release, analysis, ASan and formatting passed 20/20;
|
||
Linux CI has not run yet.
|
||
|
||
M3.5 keeps what M3.4 produces (ADR-0034). `LineageArchive` has no removal
|
||
operation at all, so retention is a property of the interface rather than a rule
|
||
someone has to remember, which is the only form of "keep extinct genomes
|
||
indefinitely" a later change cannot quietly undo. Admission requires the parent to
|
||
be present, so ancestry never dangles and the parent graph is acyclic by
|
||
construction; a duplicate identity is refused rather than overwritten. Organism
|
||
and genome identity stay separate: a death is terminal for the organism and
|
||
touches nothing about the genome, and ancestry, descendants and divergence all
|
||
resolve after every carrier has died. A lineage with no living carrier is reported
|
||
absent, never extinct, because terminal extinction needs a reconciled watermark
|
||
covering suspended members, eggs and in-flight transfers that this type cannot
|
||
see; absence is also reversible. Capacity is bounded and admission fails loudly,
|
||
since refusing to record is not deleting. NPC mutation stays undecided: the
|
||
archive records an origin event and never an actor. Nothing is serialized, so
|
||
durable retention and migration remain M7 and M8. Native Release, analysis, ASan
|
||
and formatting passed 21/21; Linux CI has not run yet.
|
||
|
||
M3.6 closes M3 by making the M3 pieces meet (ADR-0035). `strategy_for` derives a
|
||
`StrategyConfig` from ADR-0032's budget, so a strategy is what the genome already
|
||
implies rather than a second description of the same organism, and a parent
|
||
reproduces once it holds what it would invest. Founders are variants of one
|
||
ancestor diverged by ADR-0033's draw before any episode starts and admitted to
|
||
ADR-0034's archive with their parent links; every birth and death is recorded as
|
||
it happens, so the diversity a run reports has a provenance. Nothing mutates
|
||
during an episode, because autonomous divergence would settle NPC mutation, which
|
||
stays open. `evo-sim --ensemble` runs the grid and reports each cell's seeds in
|
||
two halves that are never merged. ADR-0029's driver is untouched and the M2.6
|
||
fingerprint still holds.
|
||
|
||
Two findings are recorded rather than smoothed over. Resource level never reaches
|
||
strategy derivation: founders are derived fully grown, so their construction
|
||
transition is empty and ADR-0031's per-channel `available` cannot move intake,
|
||
assimilation or investment; the resource level acts only as the nutrient pool
|
||
bounding producer growth. And the resource axis is not monotonic, so no test
|
||
asserts a direction. A sweep peaks near 8000 femtograms and falls away on both
|
||
sides, because ADR-0026 lets only one consumer bite a target per tick: the
|
||
community's income is capped at one producer bite regardless of the pool, scarcity
|
||
drives predation that concentrates mass into individuals that reach the threshold,
|
||
and abundance spreads the same income too thin to fund a birth. Separately, the
|
||
fixture's reproduction investment is pinned to the genome schema's floor because
|
||
intake scales with surface while investment scales with mass; at any larger
|
||
fraction nothing can earn a birth within a lifespan and both axes measure nothing.
|
||
That is a finding about the ADR-0031/0032 cost model, not a fixture detail.
|
||
|
||
Review of `89ad95b` found three defects, all now fixed with regressions confirmed
|
||
to fail without their fix. The harness recorded a death for every organism still
|
||
alive when an episode stopped, so a one-tick run reported no extinctions while
|
||
writing terminal records for founders that had not died; ending observation is not
|
||
death, survivors now stay living in the archive and their watched time is summed
|
||
apart from completed lifetimes. A draw that produced a genome without the
|
||
reproduction capability derived a zero investment, which ADR-0029's driver refused
|
||
outright, so seeds 10, 12 and 15 failed the whole run; the driver now runs such a
|
||
strategy and proposes no birth for it, because filtering those variants out would
|
||
have made the measured set the fertile subset chosen by a guard. And a half's
|
||
thermal shortfall was assigned rather than accumulated, so a field documented as a
|
||
total reported one episode's reading. The M2.6 fingerprint `2cd4a15f9fbe9949` is
|
||
unchanged, since only configurations the driver previously rejected behave
|
||
differently; the ensemble CLI pin was repinned because the reported facts changed.
|
||
Native Release, analysis, ASan and formatting passed 33/33; Linux CI has not run
|
||
yet.
|
||
|
||
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.
|
||
|
||
M4.1 opens M4 (ADR-0036) by defining the tier 2 record and who may act on it, and
|
||
nothing else: there is no collapse transaction, no population advance, no
|
||
materialization and no habitat geometry. A `Cohort` is validated on construction
|
||
and never mutated afterwards. Age classes each carry their own count and their own
|
||
reserve, so the record holds a distribution rather than the mean the milestone's
|
||
named risk warns about; within a class members are indistinguishable, which is the
|
||
record's declared resolution and a stated loss rather than a hidden one. No
|
||
accessor returns a mean. Totals are summed from the classes instead of stored
|
||
beside them, following the lineage archive's rule that a second tally is a thing
|
||
that can disagree. Lineage is deliberately not a field: ancestry is resolved from
|
||
the genome through the archive, so a cohort cannot contradict it or invent
|
||
parentage from membership. Residuals are integer numerators over a declared scale,
|
||
strictly below one member, and are never added to a count.
|
||
|
||
Ownership is enforced rather than described. `CohortRegistry` admits at most one
|
||
record per habitat and genome, so ECOLOGY_MODEL's "no inventory is spendable in
|
||
two tiers" is unrepresentable rather than forbidden, and replacement is refused
|
||
under a different worker, an older epoch, or a changed habitat or genome. Epochs
|
||
make a stale writer fail locally and say nothing about fencing between workers,
|
||
which stays M7 and M10. The approximation bound is carried and never computed:
|
||
M4.5 measures resolution equivalence, and carrying a bound is not meeting one.
|
||
Nothing is serialized, so `schemas/population-v1.md` pins field meaning and
|
||
invariants rather than a byte layout. All nine construction and registry guards
|
||
were confirmed load-bearing by removing each one and observing the suite fail.
|
||
Native Release, analysis, ASan and formatting passed 34/34; Linux CI has not run
|
||
yet.
|