Close M2 with a deterministic driver that owns one community and one
seeded stream, holds no inventory and emits only the terminal, feeding
and reproduction intents the earlier increments already accept. No
simulation contract changed to make the cycle run unattended.
Two limits shaped the design. Identities are never reused and slots are
capped, so one community supports a bounded number of consumer lifetimes
and is not a population. No maintenance cost exists, so a consumer that
is never eaten never dies, and inventing a starvation rule here would
settle a question ENERGY_MODEL leaves open inside a measurement harness.
The harness therefore measures many bounded episodes, taking mortality
from predation and from a configured lifespan delivered as an ADR-0027
host terminal fact. Lifespan bounds an episode; it is not senescence.
The driver must never submit a batch the community rejects, so it probes
a discarded copy each tick to size bites against the state feeding will
actually see, claims each target for one feeder, and excludes a bitten
consumer from acting. A rejected tick is reported as a driver defect
rather than absorbed as ecology.
Across 64 seeds the suite steps tick by tick, requiring exact conserved
totals at every tick and an identical report on replay, and covers both
mortality paths, slot exhaustion, tick-limit termination, lineage
attribution, episode independence and configuration rejection.
evo-sim --ecosystem reports seeded ensembles: 3,000 episodes advanced
1,093,007 ticks, all reaching extinction, with deaths reconciling exactly
against founders plus births. That demonstrates arithmetic and turnover,
not ecological plausibility; strategy constants are chosen inputs.
Native Release, clang-tidy analysis, ASan and format checks pass 11/11;
golden d61ad5bf0c928c76 is unchanged. Linux CI has not run yet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Births validated each parent against the progressively modified
candidate, so a child allocated earlier in the same batch was already
active and could fund a further birth. Two generations could appear in
one tick, which ADR-0028 forbids. The contract was already correct; the
implementation did not enforce it.
Fix parent eligibility on entry to the reproduction phase, after terminal
facts and feeding, and check every intent before applying any birth. A
rejected cascade leaves the whole tick unchanged, as before.
The regression test admits one intent whose parent is created by the
preceding intent and requires unborn_actor with balances, progress,
receipts and slot states untouched. It fails against the unguarded
implementation and passes with the guard. The same pair succeeds across
two ticks and records the grandchild ancestry. Native Release, clang-tidy
analysis, ASan and format checks were rerun and pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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>
Aeternalis Evolution, a custom-engine persistent evolutionary MMO.
This first commit establishes the project skeleton:
- Architecture and design docs: project vision, system overview,
engineering constitution, roadmap, 19 ADRs, and the simulation,
world, network, persistence and infrastructure architectures.
- Headless engineering proof: deterministic synthetic particles,
component lifecycle, explicit PRNG streams, canonical snapshots
and restored execution.
- Build and tooling: CMake 3.28+ / Ninja presets, C++23 feature
check, clang-format and clang-tidy config, format check script,
Windows check script, and a Docker build context.
- Tests: unit tests, benchmarks, a snapshot fuzz target and CLI
integration wiring.
No gameplay, renderer, network service or running deployment yet.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>