Files
aevolution/docs/engineering/VALIDATION.md
T
dingoandClaude Opus 5 8020347f9b Keep every lineage, and never call absence extinction
M3.5 retains the genomes M3.4 produces and the organisms that carried
them. The named risk is deleting extinct genomes, so the answer is
structural: LineageArchive has no removal operation at all, not a guarded
one and not a private one. 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" that a later change cannot quietly
undo. Four concepts assert that, with a positive control so the check is
known to be live rather than vacuous.

Admission requires the parent to be present, so ancestry never dangles
and the parent graph is acyclic by construction: a cycle would need one
of its members admitted before itself. A duplicate identity is refused
rather than overwritten, because overwriting is deletion renamed.

Organism identity and genome identity stay separate. A death is terminal
for the organism and touches nothing about the genome it carried;
ancestry, descendants and divergence all resolve afterwards.

The quieter risk is calling something extinct that is merely unobserved.
The archive reports living or absent and has no third answer: terminal
extinction is a policy judgement over a reconciled watermark covering
suspended members, eggs, spores and in-flight transfers, none of which
this type can see, so the word does not appear in the API. Absence is
also reversible, and a test shows a lineage regaining a carrier.

Capacity is bounded and admission fails loudly at the limit, since
refusing to record is not deleting but a silent drop would be.

The roadmap lists an NPC-mutation decision as a dependency, and
OPEN_QUESTIONS leaves it open until M12. It stays open: the archive
records an origin event and never an actor, so whether an NPC may
diverge changes nothing here.

Two clang-tidy findings were fixed rather than suppressed. std::map
members made the archive's move potentially throwing, because MSVC's map
move constructor allocates; sorted vectors replaced them. A wrapper
struct holding a Genome by value had the same problem, since ADR-0030
made Genome copy-only, so genomes are stored directly under their own
id(). The redundant carrier tally went with it: carriers are counted from
the organism records, so no second tally can drift.

Native Release, clang-tidy analysis, ASan and format checks pass 21/21.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-23 16:55:36 -04:00

43 KiB
Raw Blame History

Validation report

Recorded 2026-09-19. Latest verified Linux delivery: run 1402 passed on 4c2cc04ac47d37c6191a9ef02d4bbba716a930dc. Native checks apply to base commit 8ab48d3 plus the foundation-delivery working changes committed with this report. Simulation rules and snapshot format remain version 1; the only C++ change is benchmark metadata. Results below distinguish executed checks from pending Linux/cluster gates.

Tools and host

  • Windows NT 10.0.26200, AMD Ryzen 7 9800X3D, 8 cores / 16 logical processors.
  • MSVC 19.44.35217.0, CMake 3.31.6-msvc6, Ninja 1.12.1.
  • clang-format and clang-tidy 19.1.5 (Visual Studio LLVM tools).
  • kubectl 1.31.4 / Kustomize 5.4.2 for offline manifest rendering.

Executed native checks

Command Observed result
./tools/windows-check.ps1 -Preset debug -Action check Configure/build passed; 5/5 CTests passed
./tools/windows-check.ps1 -Preset release -Action check Configure/build passed; 5/5 CTests passed under NDEBUG
./tools/windows-check.ps1 -Preset analysis -Action check clang-tidy/warnings-as-errors build passed; 5/5 CTests passed
./tools/windows-check.ps1 -Preset asan -Action check MSVC AddressSanitizer build passed; 5/5 CTests passed; this is NOT UBSan
./tools/windows-check.ps1 -Preset debug -Action format Passed with clang-format 19; repeated twice in one shell after helper fix
./build/release/evo-sim --seed 123456 --entities 8 --ticks 1000000 --verify-replay Exit 0; replay_verified=true; hash fab22c2e8ae1c379
./build/release/evo-benchmark Exit 0; MSVC 1944 Release, seed 123456, 10000 entities, 1000 ticks, 0.0210666 seconds, hash 3bad6db1612cbd1
Git Bash bash -n tools/ci/linux-check.sh and bash -n tools/ci/publish-image.sh Syntax checks passed; no Linux execution implied
kubectl kustomize deploy/kubernetes/dev Rendered Job, ServiceAccount and NetworkPolicy in evolution-dev; final render pins the verified run-1402 image

CTest covers the independently frozen 1000-tick fingerprint d61ad5bf0c928c76, seeded replay properties, malformed/semantic snapshot rejection, entity lifecycle, capacity/overflow, telemetry and CLI file continuation/alias protection. The expected-failure harness confirms tests remain active in Release.

The benchmark is a single uncontrolled wall-clock observation, not a performance threshold or an MMO capacity estimate. Its initial compiler output accidentally used hexadecimal; the stream now returns to decimal and reports MSVC 1944.

Gitea evidence

The maintainer's run 1399 on 8ab48d3a5639121693f5881b600482e870b49f05 completed successfully. API job records confirm verify (configure/build/CTest) and publish (Docker build/push) succeeded on runner theraborn-runners-runner-0, label ubuntu-22.04. This is evidence for the original workflow, not the expanded sanitizer/analysis jobs added in this change. Exact Linux tool versions and expanded-run results appear below; a runner label is not a compiler version.

Limitations and next gates

  • Local Docker Desktop has no running Linux engine. Container checks must run on the configured Gitea runner; no local container success is claimed.
  • Expanded Linux GCC14/Clang19, ASan/UBSan, TSan and libFuzzer evidence is recorded below. TSan currently validates a sequential kernel, not future concurrency.
  • Sandbox process restrictions stalled native Ninja and blocked Git Bash signal pipes. Those attempts were stopped; checks reran successfully outside sandbox.
  • Repeated VsDevCmd initialization grew PATH beyond cmd's limit. The helper now reuses the matching x64 environment and deduplicates PATH; repeated checks pass.
  • The maintainer reports Argo setup, but this workspace has no Kubernetes context. No dev Job completion or cluster admission result is recorded yet.
  • No biology, network/load, durable server recovery or backup restore exists. Those remain M2, M7/M8 and later gates, not failing or passing foundation tests.

Update this report with run URL, tested commit, image digest and Job result when those checks execute. Never overwrite a golden merely to make CI pass.

Expanded Linux run 1400

Run 1400, commit 9e412736d9: GCC14 Debug and Release, Clang19 analysis and ASan/UBSan each passed 5/5 tests. Formatting passed. The seeded fuzz smoke completed 10000 cases with no reported failure. CMake 3.28.3, GCC 14.2.0, Clang/format/tidy 19.1.1, Linux 6.8.0-110-generic x86-64. Million-tick hash matched Windows (fab22c2e8ae1c379); benchmark hash matched too (3bad6db1612cbd1), with 0.0674131 seconds observed for 10000 entities * 1000 ticks on the CI host.

TSan compiled but all executions failed before main: its runtime could not call personality(ADDR_NO_RANDOMIZE) inside the Docker build sandbox. The image job was skipped, as required. This is not recorded as a TSan pass. The follow-up isolates execution in a container with the narrowly constrained profile from ADR-0020; its result must be recorded after execution.

Successful delivery run 1402

Run 1402, commit 4c2cc04ac4: every job succeeded. The general checks reused Docker's valid cache for unchanged checked sources; their full execution also passed in run 1401. TSan executed all five CTests successfully in 2.71 seconds using the scoped profile and writable tmpfs outputs. Run 1401 had first exposed a non-root tmpfs permission error; setting explicit mode=1777 on these isolated scratch mounts fixed it. No test was disabled or ignored.

The runtime image built, ran the restricted replay smoke test and was pushed to:

registry.aeternalisgames.com/aeternalis/aevolution:sha-4c2cc04ac47d37c6191a9ef02d4bbba716a930dc-run-6-1

Registry digest: sha256:8fce2b462c9907f38d3fb832afeb70d0bff068dd832b2171e861186dbcb8e6b9.

The dev manifest pins this digest. This proves build/test/image delivery; Argo application mapping and Kubernetes Job completion remain unverified locally.

M1.5 native ECS experiment

Opt-in target evo-ecs-experiment (EnTT4 pinned in ADR-0021), based on 1c6e6e1 plus this experiment's changes. MSVC Release contract checks passed, including 72 seed/density/count combinations, hand-calculated arithmetic, canonical equality, restore continuation, retired-ID rejection, malformed snapshot checks and allocator balance. The final clang-tidy build/test passed after tightening the process-boundary diagnostic catch. MSVC ASan passed on the final source. Baseline Release CTest remained 5/5 and format-check included the experiment. No simulation rule/golden changed.

Commands: configure release/analysis/asan with -B build/ecs[-analysis|-asan] -DEVO_BUILD_ECS_EXPERIMENT=ON, build target evo-ecs-experiment, then ctest --test-dir <directory> -R ecs-experiment --output-on-failure. Seven measured samples plus warmup are retained in results/ecs-msvc1944.jsonl; protocol, build observations and scope limits are in ECS_EVALUATION.md. The Linux experiment CI job is pending its first pushed run; no Linux experiment success is claimed yet.

M1.5 Linux evidence

Run 1404, source bf7d60b7cd: every job passed. The new ci-ecs stage explicitly prepared the pinned header/license, then built and ran the experiment under GCC14 Release, Clang19 ASan/UBSan and Clang19 analysis. All three contract invocations passed. Raw measured GCC samples are retained at results/ecs-gcc142.jsonl; all 56 fingerprints match corresponding Windows samples. No production rule or snapshot-format change occurred. This supersedes the pending Linux experiment note above. The final follow-up edits only record results and decision scope; production ECS adoption remains deferred.

M1.6 sequential scheduler (2026-09-19)

Native commands: tools/windows-check.ps1 -Preset release -Action configure, clang-format on changed C++ files, cmake --build --preset release, ctest --preset release; then tools/windows-check.ps1 -Preset analysis -Action check, tools/windows-check.ps1 -Preset asan -Action check and Release -Action format. All three configurations passed 5/5 CTests; clang-tidy and format-check passed. Tests execute under NDEBUG and cover six batch permutations across 32 seeds, an independent direct-lifecycle reference, ordered receipts, restore continuation, rejected conflicts and malformed admission, the 1,024-command boundary, full entity capacity and tick/ID exhaustion. Golden d61ad5bf0c928c76 remains unchanged.

The copy-and-commit implementation allocates before publishing world state and statically checks noexcept publication/receipt moves. Allocation-failure injection was not run. No scheduler throughput claim, concurrency validation, durable input journal or Kubernetes execution is implied.

Gitea run 1407 passed all four jobs for source b620edfd6f8097172acf055402a24620cb078358: Linux checks, the ECS experiment, separate TSan, and image smoke/publication. This closes the pending Linux validation for M1.6. The maintainer's independent dev image pin from 20e609d was preserved during rebase. Kustomize renders the three expected dev resources successfully; no cluster execution is claimed.

M1.7 spatial queries (2026-09-19)

Release and MSVC ASan passed 5/5 CTests. Tests cover periodic-image reference comparison (32 seeds × 3 lifecycle/restore phases × 24 queries), hand-checked seams/corners/inclusive radii, empty/full capacity, invalid centers and maximum u32 radius. Queries leave snapshots unchanged; existing v1 goldens remain intact. Native commands use tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and Release -Action format. Initial analysis flagged an unnecessary test-helper vector copy; the helper now takes a const reference. Final analysis, Release, ASan and formatting passed after applying the helper's required line wrapping. Linux validation is recorded below.

build/release/evo-spatial-benchmark.exe produced 72 measured records plus metadata in results/spatial-msvc1944.jsonl. One warmup and three samples per scenario; 1k/10k/100k entities, 128 queries, uniform/clustered positions, four radii. Timing includes result allocation, destruction and checksum work, excludes setup; no performance threshold. Desktop CPU load was not isolated. No cluster changes are required for this library increment.

Gitea run 1409 passed all four jobs for source 9b19509673d88683ee72e093e42534bfe151f928: Linux checks, ECS regression, separate TSan and image smoke/publication. All 72 spatial benchmark checksums and match counts agree with Windows. Raw Linux measurements are in results/spatial-gcc142.jsonl; 24 native scenarios also have identical checksums across their three repetitions. No deployment manifest, rules version, snapshot format or golden was changed.

M2.1 finite inventory ledger (2026-09-19)

Native Release, analysis and MSVC ASan each passed 6/6 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and Release -Action format. Initial clang-tidy rejected the Element enum's oversized base type; changed to u8 and reran all configurations successfully.

The new independent ledger test checks typed energy/mass separation, finite-source exhaustion, explicit heat transfer, intermediate overdraft, whole-transaction rollback, retry/duplicate action semantics, invalid reservoir IDs, maximum batch and reservoir counts, opening-total overflow and exact u64-limit transfers. 32 seeded runs × 31,250 transactions = one million transactions, each checked against independent reference balances, a replay branch and recomputed per-channel totals. This is transfer replay, not serialized recovery or an ecosystem run. Final ledger tests took 0.63s Release and 7.62s ASan locally; not controlled performance measurements. Existing particle goldens remain unchanged.

Allocation-failure injection, durable ledger recovery and cross-ledger ownership are not tested or implemented. Rates and conversions are absent, so rounding residuals cannot occur in this transfer-only scope.

Gitea run 1411, source 8fd3591b0e37aaecf00a6410a5926745a031cb6f, passed the Linux checks, ECS regression and separate TSan jobs. Each main Linux configuration passed 6/6 CTests. Ledger-suite times were 3.34s GCC Debug, 0.37s GCC Release, 2.46s Clang analysis and 8.78s Clang ASan/UBSan; these are CI test durations, not controlled performance benchmarks. The image smoke/publication job also passed, completing all four jobs. No deployment image pin was changed.

M2.2 finite producer process (2026-09-19)

Native Release, clang-tidy and MSVC ASan passed 7/7 CTests; format-check passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and Release -Action format. The producer suite compares hand-calculated ticks and 32 seeds × 1,000 ticks against a small-domain cumulative arithmetic reference, an independent replay branch and per-tick energy/element conservation audits. It covers invalid config/ticks with unchanged state, fractional capture/growth, efficiency endpoints, finite source exhaustion, all four limiting elements, zero capture, maximum u64 capture with 50% carried conversion, and maximum recipe and growth-cost multiplication. Particle goldens remain unchanged.

Allocation-failure injection and tick-counter exhaustion were not exercised; the latter has an explicit guard but no arbitrary-state restore API. Tests use in-memory copies, not serialized recovery. No photosynthetic chemistry, metabolic model, database integration, throughput guarantee or deployment is claimed. Gitea run 1413 passed all four jobs for source af293b8b50cbb506a49dfff10c6cc92307e16aca: Linux checks, ECS regression, separate TSan and runtime image smoke/publication. The initial push was delayed by a tool approval-review usage limit; retry succeeded after the maintainer resumed work. No deployment image pin was changed.

M2.3 shared feeding community (2026-09-20)

Native Release, clang-tidy and MSVC ASan each passed 8/8 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and Release -Action format. The new suite checks hand-calculated capture/feeding, producer-to-consumer and consumer-to-consumer predation, heat/waste outputs, terminal actor rejection, full-tick rollback, competing resource requests, duplicate sequence/consumer admission, per-channel intake caps, invalid actors, config/capacity limits and u64 assimilation endpoints. 32 seeds × 200 ticks compare reordered input batches, receipts, full balances and producer progress, with independently recomputed energy and elemental totals. Standalone producer and existing particle golden tests remain unchanged and passing.

No serialized recovery, allocation-failure injection, spatial reach/perception, physical injury, corpse handling or persistent-world integration was tested or implemented. These are co-located synthetic process fixtures.

Gitea run 1415 passed all four jobs for source b7dd466f57f385d6a8ffccfaa69f639077545587: Linux checks, ECS regression, separate TSan and image smoke/publication. No deployment image pin was changed.

M2.4 terminal inventory and decomposition (2026-09-20)

Native Release, analysis and MSVC ASan passed 8/8 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and Release -Action format. Tests preserve corpse inventories on death, suppress producer activity immediately, reject repeated/invalid terminal events and roll back death with later invalid feeding. Sixteen seeds × 256 ticks compare a closed-form depletion reference, reversed terminal-event order, per-tick budgets, inventories and conservation. Additional cases cover shared corpse/waste limits, mixed and zero channel caps, u64-maximum inventories, diagnostic rollback, and returned nutrients funding producer structure on the next tick.

The existing feeding, standalone producer, ledger and particle tests pass unchanged. This does not validate reaction chemistry, actual death causes, corpse scavenging, serialized recovery, allocation-failure injection or persistent history. There is no deployment change.

Gitea run 1417 passed all four jobs for source e17a9a7279d6bde736261c0c33abe46108e1f622: Linux checks, ECS regression, separate TSan and image smoke/publication.

M2.5 funded reproduction (2026-09-21)

Native Release, analysis and MSVC ASan passed 8/8 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. The first format run rejected three wrapped test declarations; clang-format 19.1.5 rewrote them and Release was rebuilt and rerun.

Tests cover hand-calculated endowment and construction overhead, the endowment floor, per-channel insufficiency with abundant energy, zero and oversized investments, reserved slots rejected as feeding targets, corpses and ancestry subjects, the producer rejected as a parent, terminated and unknown parents, zero/duplicate sequences, two intents naming one parent, oversized batches, capacity exhaustion rejecting the whole tick, absent identity reuse after a child dies and decomposes, ancestry surviving both deaths, and construction endpoints of 0 and 1000 including a paid-for zero-endowment child. 32 seeds × 4 ticks × 2 births compare reversed intent order against balances, producer progress, birth receipts and independently recomputed conservation. A u64-maximum investment endows exactly and conserves. Default zero capacity leaves the M2.4 reservoir layout, feeding, producer, ledger and particle tests unchanged; golden d61ad5bf0c928c76 is intact.

Review of c84a701 found one defect (2026-09-22): 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 second birth. Two generations could therefore appear in one tick, which ADR-0028 forbids. Eligibility is now fixed on entry to the reproduction phase, after terminal facts and feeding, and checked for every intent before any birth is applied. The contract itself was already correct and did not change. The regression test admits one intent whose parent is created by the preceding intent and requires unborn_actor with the entire tick unchanged; it was confirmed to fail against the unguarded implementation and to pass with the guard. The same pair succeeds across two ticks, recording the grandchild ancestry. All four native configurations were rerun after the fix.

Allocation-failure injection, serialized recovery of states/parents/origins and long-run ecosystem behavior were not exercised. This fixture defines no reproductive strategy, fecundity, mutation, gestation, spatial placement or account ownership, and no deployment manifest or image pin changed. Linux validation is pending its first pushed run; no Gitea result is claimed for this increment yet.

M2.6 measured ecosystem episodes (2026-09-22)

Native Release, analysis and MSVC ASan each passed 11/11 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. Formatting rejected 25 wrapped declarations on the first run; clang-format 19.1.5 rewrote them and Release was rebuilt and rerun. Three CTest cases are new: ecosystem-contracts, cli-ecosystem pinned to fingerprint 2cd4a15f9fbe9949, and cli-ecosystem-conflict, which requires the CLI to reject --ecosystem combined with proof-run options.

The suite checks a solitary founder that only ages, a hand-checked predation retirement, births exhausting exactly the reserved slots, tick-limit termination with survivors, configuration rejection, and two episodes interleaved without observing each other. Across 64 seeds it steps tick by tick, requiring that the driver never provokes a rejected batch and that conserved totals are identical at every tick, then replays each seed and requires an identical report. That ensemble advanced 22,804 ticks with 879 births, 730 predation deaths, 277 lifespan deaths and extinction in all 64 episodes, episode length 73 to 463 ticks.

build/release/evo-sim.exe --ecosystem --seed 0 --episodes 3000 advanced 1,093,007 ticks in 1.34 s, with 41,138 births, 33,984 predation deaths, 13,154 lifespan deaths, extinction in all 3,000 episodes, episode length 50 to 497 ticks and fingerprint 130d7725c0dc8b16. Deaths equal founders plus births exactly (6,000 + 41,138 = 47,138), so every process died once and no producer was grazed out: the producer always retains captured energy, so its whole inventory never reaches zero. The elapsed time is one uncontrolled wall-clock observation, not a performance threshold.

Review of eaf58f2 found one defect (2026-09-22): the CLI validated mode options in one direction only. --ticks was accepted and ignored under --ecosystem, and --episodes/--tick-limit were accepted and ignored without it, so a measurement script could exit zero while running the other workload. The parser now records which options were supplied and rejects any that do not belong to the selected mode, in both directions. Six CLI cases cover this; cli-ecosystem-rejects-ticks and cli-episodes-require-ecosystem are the two genuine regressions, while the entities, save and verify-replay cases were already rejected and add coverage. The remaining shared options were audited: --seed and --output are valid in both modes, and --load conflicts were already enforced. CTest is now 16 cases, all four native configurations were rerun, and 2cd4a15f9fbe9949 is unchanged.

This measures arithmetic conservation and turnover, not ecological plausibility. Strategy constants, lifespans and the targeting rule are chosen inputs. There is no maintenance cost, starvation rule, perception, spatial gate, genome or heritable variation, so lineages differ only by founder strategy. Episode state is not serialized, allocation failure is not injected, and no population abstraction exists. Golden d61ad5bf0c928c76 and every earlier suite are unchanged. No deployment manifest or image pin changed. Linux validation is pending its first pushed run; no Gitea result or cross-platform fingerprint agreement is claimed yet.

M3.1 immutable genome record (2026-09-22)

Native Release, analysis and MSVC ASan each passed 17/17 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. Formatting rejected three wrapped declarations on the first run; clang-format 19.1.5 rewrote them and Release was rebuilt and rerun. genome-contracts is the one new CTest case, covering a new evo::biology library that nothing else links.

Tests cover founder and descendant records, unordered drafts producing byte-equal canonical records, digests differing for identical capabilities from different origins, and every ancestry rule: zero identity, zero origin, zero development version, a zero parent, a self parent, two parents and a repeated parent. Schema rules cover an empty record, each of the three required capabilities removed in turn, a duplicate kind, an unknown kind, an unknown prerequisite bit, and both inclusive boundaries of all seven declared ranges accepted with one below and one above each rejected. Graph rules cover a declared prerequisite naming an absent capability, self, mutual and three-node cycles, a valid ordering using the same edges without the closing one, and a cycle closed by a mandated rather than a declared edge.

Encoding tests cover the round trip, byte-exact re-encoding, truncation at every length from zero to one byte short, one trailing byte, an oversized buffer, a corrupted magic, and every single-byte corruption of the full record. Three cases reseal the checksum after editing so the later checks are reached rather than masked: a rewritten genome ID is caught by the digest, a future schema version fails closed, and non-canonical record order is caught as a duplicate kind. A parent count beyond the reserved room and a capability count beyond the schema are both refused before the corresponding region is read.

Coverage limitation: in schema 1 every mandated capability is also a required one, so the presence half of the mandate check is reachable only through declared prerequisites, which is tested. The mandated edges do take part in the cycle closure, which is tested. A later schema that mandates a capability without requiring it would exercise the remaining branch; this is recorded rather than covered by a test that could not fail.

Review of 8584eb1 found two defects (2026-09-22). First, Genome had implicit move operations, so moving one emptied the source's capabilities while leaving its identity, origin and digest intact: a record that still reported ID 7 but whose encoded bytes no longer decoded. That contradicted the documented invariant directly. The type is now copy-only, which suppresses the implicit moves so a move decays to a copy, and the invariant holds for every operation. The new move tests were confirmed to fail without the fix: the Debug and ASan builds exit 1 at runtime, and the Release build does not compile at all, because MSVC proves the moved-from comparison always throws and rejects the unreachable code under warnings-as-errors. clang-tidy then flagged the deliberate decaying moves in the tests as performance-move-const-arg; those two lines carry a NOLINT explaining that the decay is the contract under test.

Second, the encoding tests compared the current encoder against the current decoder, so a coordinated change to layout or digest would have passed while breaking existing v1 records. A frozen 83-byte fixture now holds one schema 1 founder record. Every structural byte was verified by hand against schemas/genome-v1.md before being frozen: magic, both versions, ID 7, origin 1, zero parents, three records, kinds 0/1/5 with parameters 400/120/5000, and the 56 + 9N length. The digest 9b2cdedef16ac87f and the trailing checksum are computed values frozen alongside them. The fixture is asserted in both directions: the encoder must still produce those bytes, and the decoder must still read them into the expected record. It is a golden and must not be edited to make a test pass.

No genome affects any simulation, and nothing links the new library except its own tests. The M2 process fixtures still duplicate founder strategies and do not read the record. Development, phenotype derivation, mutation, recombination, multi-parent heredity, migration between schema versions and any persistent genome archive are not implemented. The encoding is a local record format, not a network protocol or durable storage, and neither the digest nor the checksum is an authenticity claim. Golden d61ad5bf0c928c76 and the ecosystem fingerprint 2cd4a15f9fbe9949 are unchanged. No deployment manifest or image pin changed. Linux validation is pending its first pushed run; no Gitea result is claimed yet.

M3.2 development and phenotype (2026-09-22)

Native Release, analysis and MSVC ASan each passed 18/18 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. development-contracts is the one new CTest case, in the existing evo::biology library, which still nothing else links. No existing suite changed.

The fixture genome uses a target size of 8,000,000 fg, which is an exact 20 micrometre cube at the declared density, so every derived value is hand-calculable and is asserted as a literal: structural mass 8,000,000, extent 20, surface 2,400, membrane mass 28,800,000, total 36,800,000 and maintenance 160,000 picojoules per tick. Half-built, damaged and maximum-size cases are hand-calculated the same way, including the 1e9 fg body that is an exact 100 micrometre cube with an uptake rate of exactly the reference surface, and the 999,999,999 fg body one cubic micrometre short of it, whose extent is 99.

Determinism is checked over 45 growth and temperature combinations, each derived twice and compared, with more growth never yielding less structure. Damage is checked to change the phenotype while leaving the genome's encoded bytes and content digest identical, which is the M3.2 risk stated in the roadmap. Capability prerequisites are checked both ways: without the capability a component is zero at any size, and with it uptake scales with surface while movement speed does not. Thermal shortfall is checked inside tolerance, symmetrically outside it, and without the capability, and is confirmed to change no other derived value. Unsupported rule versions and out-of-range growth fail closed through both entry points.

Plans are checked for the full funded step, for the exact largest affordable step one femtogram short of it, for no growth with no material, for a finished organism, for clamping the last step to the target rather than overshooting, and for never repairing damage. The declared flooring is pinned rather than hidden: a body whose mass floors to zero advances its growth counter for no material, which grants no structure because none exists at that size either way.

Coverage limitation: the overflow guards are unreachable through the public API at schema 1 ranges, because the largest admissible genome produces a total mass of about 7.2e11 femtograms, eleven orders of magnitude below the u64 limit. They are kept as guards for later schema ranges and are recorded here rather than covered by a test that could not fail.

No organism develops, nothing links the library except its own tests, and no inventory moves: a plan reserves nothing and pays for nothing. The transfer half of ApplyDevelopment, energetic budgets, repair, ageing, starvation, mutation and morphology are not implemented. Golden d61ad5bf0c928c76, ecosystem fingerprint 2cd4a15f9fbe9949 and the frozen genome fixture are unchanged. No deployment manifest or image pin changed. Linux validation is pending its first pushed run.

M3.3 metabolic budgets (2026-09-23)

Native Release, analysis and MSVC ASan each passed 19/19 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. metabolism-contracts is the one new CTest case. evo_biology now links evo::accounting and evo_processes links evo::biology; no existing suite changed and no existing fixture reads genomes.

Every budget is asserted as a hand-calculated literal against the same 20 micrometre cube fixture as M3.2: body 24,160,000 / 2,640,000 / 3,280,000 / 6,720,000 femtograms across C/N/P/other, maintenance 160,000 and movement 184,000 picojoules per tick, intake 240,000 picojoules and 2400/720/240/1440 femtograms, and a reproduction investment of 11,040,000 femtograms priced at 441,600 picojoules. Construction is checked to compose each compartment separately rather than by one blended ratio, and to agree exactly with what plan_development reports as material and energy.

The non-uniformity the increment exists to demonstrate is tested directly. Doubling membrane thickness raises body matter to 65,600,000 femtograms, maintenance to 304,000 picojoules and the movement cost, shifts the carbon share upward because membrane is the carbon-rich compartment, and leaves intake limit, speed, assimilation and structural mass identical; the mass and maintenance ratios are asserted to differ, so no single multiplier could produce this. Growth is tested the same way: uptake follows surface while maintenance follows mass, and their ratios differ.

Mass splits are checked to conserve at four awkward target sizes and four growth fractions, where every share floors and the last channel absorbs the remainder. An absent capability is checked to yield a zero budget rather than a default, and unknown rule versions and out-of-range growth fail closed.

The genome-to-ledger path is exercised end to end: a derived ConsumerConfig drives a real FeedingCommunity tick, the ledger totals are identical before and after, and a bite one femtogram past the derived cap is refused by the existing M2.3 contract. The opening inventory is checked to be exactly the caller's.

Review of be71d4f found one defect (2026-09-23): construction composed the mass difference rather than differencing the two composed bodies, which discards the rounding the existing body already carries. At target mass 1001 growing from 10 to 60, it funded C25 N7 P2 other16: the right total, but nitrogen and phosphorus one short each and other two over, so spending the budget could not produce the body the same rules derive. Construction is now the per-channel difference between the composed bodies, which funds C25 N8 P3 other14 for that case.

Because the remainder rule is not monotone per channel, that difference can be negative on a channel, so construction became a transition with an intake and a release rather than a single requirement: a body growing from 13 to 14 femtograms acquires one carbon and one nitrogen while freeing one from other. The release is a rounding artifact bounded by a few femtograms, not excretion.

A follow-up review found the affordability half of the same problem: a transition could require more of an element than was available, because the check compared net mass. A step growing a body from 13 to 14 femtograms nets one femtogram but acquires a carbon and a nitrogen while freeing one of other, and released other pays for neither. The environment now states availability per ledger channel rather than as one pool, since a pool cannot say that carbon is plentiful while nitrogen is not. plan_development keeps a total-mass bound, sound because net never exceeds gross but not an authority, and metabolic_budget narrows it to the largest step whose own intake fits channel by channel and reports the growth that step funds. That revises ADR-0031 and is recorded there.

The affordability tests place a single femtogram in each channel in turn and require that no step needing a different element is funded, that nothing is acquired beyond what is present, and that the mass-only plan would have admitted the step; a carbon and a nitrogen together then fund it exactly. Across six target sizes by seven growth fractions by four stock levels, every reported intake is checked to fit the availability channel by channel and never to exceed the step the plan proposed. These tests were confirmed to fail with the per-channel check removed.

A third review found the availability bound itself could wrap: summing four unrestricted u64 channels with 2^62 in each reaches exactly 2^64, so the total read as zero and both planning and budgeting refused growth that a billion femtograms per channel funded. The sum now saturates, which is also the right answer since no step can need more than u64. Regressions in both suites use that exact 2^62 case and a single saturated channel, and require the same step a billion per channel funds; both were confirmed to fail without saturation. The equivalent helper in metabolism.cpp is applied only to inventories derived from bounded phenotype masses, never to caller input, so it is left unsaturated rather than given a branch no test could reach.

The invariant held + intake - release == reached is now asserted per channel for the reviewer's exact case, for the releasing case, across six target sizes by seven growth fractions by four material budgets, and across a forty-step walk from nothing to full growth where the accumulated intake and release are checked against the whole history. The net of every transition is also asserted to equal what plan_development charges material for. These tests were confirmed to fail against the previous implementation.

Coverage limitation: as in M3.2, the overflow guards are unreachable through the public API at schema 1 ranges and are recorded rather than covered by a test that could not fail. The small integer helpers are duplicated between development.cpp and metabolism.cpp rather than shared through an internal header.

No organism spends any budget: nothing consumes maintenance, movement or construction, and no starvation, death or repair rule exists. The constants are chosen for legible magnitudes, not balance. Golden d61ad5bf0c928c76, ecosystem fingerprint 2cd4a15f9fbe9949 and the frozen genome fixture are unchanged. No deployment manifest or image pin changed. Linux validation is pending its first pushed run; no Gitea result is claimed for any increment since b01a824.

M3.4 seeded mutation candidates (2026-09-23)

Native Release, analysis and MSVC ASan each passed 20/20 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|analysis|asan> -Action check and debug -Action format. mutation-contracts is the one new CTest case, in the existing evo::biology library. No existing suite changed.

The eligible set for the founder fixture is pinned by hand rather than observed: nine operators, derived from the schema by the rules that make them eligible. Energy conversion and membrane can adjust either way, movement, ingestion, reproduction and thermal tolerance can be acquired, target size can adjust up but not down because its 9,999,999 step would fall below the minimum from 8,000,000, and no required capability can be shed. Over 2,000 seeds the offers are exactly that set and nothing else.

Uniformity is checked to within a fifth of each operator's exact share, about six standard deviations for 8,000 offers across nine operators. That test was confirmed to fail when the draw was replaced by taking the first eligible operators, which is the shape a biased offering would take. The rejection sampling that removes modulo bias is correct by construction rather than test-verified: over nine bins with 64-bit draws the bias it removes is about one part in 10^18 and no test at this scale could observe it. That is recorded rather than claimed as covered.

Stability is checked both ways: the same context always returns the same candidates, while a new event index, seed, stream or growth state returns a different draw. Selection is checked to refuse an operator that was never offered, a moved event index, a changed growth state, a tampered offer and a different parent genome, each with its own error. Boundary operators are checked to be absent rather than clamped at both ends of a range, and a capability another one declares as a prerequisite is checked to be unsheddable while the dependent capability itself remains sheddable. Every offered candidate is selected in turn and its successor checked to validate, to record parent 7, and to survive a decode; the reported maintenance and mass are checked to equal what metabolic_budget charges that successor.

Review of 5497f4d found one defect (2026-09-23): selection established a stale context by comparing regenerated candidate lists, which cannot establish it. Four of nine operators is only 126 distinct lists, so different contexts draw the same list routinely, and an offer from event 1 was accepted under event 239. An offer now records the parent's identity and digest and the context itself, and selection compares those directly before anything else. Because they then determine the draw, a list that still differs means the offer was altered, which is now its own error rather than a context having moved.

The regression searches for a context whose draw collides with the offer's, asserts that such a collision exists rather than assuming it, and requires that selection still rejects it. It was confirmed to fail against the previous implementation. Rewriting the offer's recorded context to name the colliding one is checked to be accepted, and should be: those candidates genuinely are what that context draws, so the result is a legitimate offer for it rather than a forgery. Editing a candidate is checked to be caught as an altered offer.

No organism mutates and no fixture calls any of this. Candidate count, context window, mutation cost as a game rule, inherited versus acquired expression, NPC mutation and recombination remain open and are not settled here. Golden d61ad5bf0c928c76, ecosystem fingerprint 2cd4a15f9fbe9949 and the frozen genome fixture are unchanged. No deployment manifest or image pin changed. Linux validation is pending; no Gitea result is claimed since b01a824.

M3.5 lineage retention (2026-09-23)

Native Release, analysis and MSVC ASan each passed 21/21 CTests; formatting passed. Commands: tools/windows-check.ps1 -Preset <release|asan|analysis> -Action check and debug -Action format. lineage-contracts is the one new CTest case, in the existing evo::biology library. No existing suite changed.

Retention is asserted as a property of the type, not only of its behaviour: four concepts check that the archive offers no erase, remove, clear or prune, with a std::map positive control so the checks are known to be live rather than vacuously true. An earlier attempt used bare requires-expressions, which MSVC diagnoses eagerly for a non-dependent type, and a std::vector control, which was wrong because vector::erase takes an iterator rather than a key; the concept correctly reported false and the control was corrected rather than the assertion weakened.

A branching fixture of five genomes over three generations is used throughout. Tests cover a genome outliving both organisms that carried it with its record, ancestry, children and organism terminal ticks intact; ancestry and descendants resolving through a genome whose only carrier died; common ancestors for siblings, cousins, a genome against itself and two separate founders; refusal of a duplicate identity, a child admitted before its parent and a full archive; death being terminal against repeat, reversal and rebirth; and absence being reported for every lineage that has no living carrier, including one that gains a carrier again afterwards. The capacity case admits the full 4,096 genomes as one chain, checks that the refusal leaves every earlier record intact, and walks the 4,096-deep ancestry.

The implementation was changed twice under clang-tidy rather than suppressed. std::map members made the archive's move potentially throwing, because MSVC's map move constructor allocates a sentinel node; sorted vectors replaced them, which also matches the rest of the codebase. A wrapper struct holding a Genome by value then had the same problem, because ADR-0030 made Genome copy-only, so genomes are now stored directly and identified by their own id(). The redundant per-genome carrier tally was dropped in the same change: carriers are counted from the organism records, so there is no second tally that could drift.

Nothing is serialized, so no history survives a process, and no fixture calls any of this. Terminal extinction is not claimed anywhere, durable retention and migration are M7 and M8, and NPC mutation remains undecided. Golden d61ad5bf0c928c76, ecosystem fingerprint 2cd4a15f9fbe9949 and the frozen genome fixture are unchanged. No deployment manifest or image pin changed. Linux validation is pending; no Gitea result is claimed since b01a824.