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>
1.9 KiB
Architecture decision records
Locked requirements outrank these records. Review architecture, ADRs, public contracts, tests, then implementation. Stop expanding implementation on conflict.
Adopted for proof applies only to the bounded initial headless slice. Proposed recommends without adopting a dependency. Deferred requires a named experiment. Later Accepted and Superseded preserve rationale. Proof choices do not silently settle gameplay or production infrastructure.
Records 0001–0015 cover language, build, dependencies, tests/benchmarks, ECS, ticks, randomness, serialization, units, errors, threads, logging, PostgreSQL, messaging and metrics. 0016–0019 cover durability/ownership, networking/security, infrastructure and voxels. 0020 scopes Gitea delivery and the stateless dev Job. Each record has the eight required sections. 0021 authorizes the opt-in ECS comparison only, not a production dependency. 0022 adopts the bounded sequential lifecycle-command scheduler for the proof. 0023 defines local periodic neighborhood queries and a measured linear baseline. 0024 adopts finite, typed energy/matter inventory transfers for M2.1. 0025 scopes finite capture, growth recipes and residual accounting for M2.2. 0026 adds shared community ownership and bounded synthetic feeding for M2.3. 0027 adds terminal inventory ownership and budgeted nutrient return for M2.4. 0028 adopts funded reproduction, bounded slot capacity and retained lineage IDs. 0029 scopes the deterministic ecosystem driver and bounded measured episodes.
Every dependency adoption records exact version/commit and integrity hash, transitive license obligations, maintenance/security review, owner and removal boundary. Candidate performance and binary-size comparisons are hypotheses until benchmarked. Primary sources were reviewed during the initial September 2026 design. No unadopted candidate is a link dependency of the proof.