Derive a phenotype from the genome without touching it

M3.2 adds derive_phenotype and plan_development as pure integer
functions of a genome, a growth state and an environment. Nothing is
stored: a phenotype is recomputed from retained inputs rather than
cached, so a cached copy can always be checked against a recomputation.

The risk this increment was scoped against is confusing the genome with
runtime damage. Growth and damage live in a separate state that no
function may write back, and no entry point takes a mutable genome.
Damage changes the phenotype and leaves the encoded bytes and content
digest identical, so heredity cannot carry acquired condition.

The genome's development version selects a rule set, which is what makes
that field worth carrying; an unknown version fails closed rather than
deriving under the wrong rules. Version 1 declares every constant. The
shape model is explicit rather than implied: the body is a cube of
uniform declared density, so extent is an exact integer cube root and
surface is six extents squared. Membrane mass follows surface and the
genome's thickness, maintenance follows total 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, never a partial one and never
a grant. It reserves nothing and pays for nothing: the matching transfer
does not exist until M3.3, and an apply that moved no inventory would
look like a committed operation while conserving nothing.

The fixture genome is an exact 20 micrometre cube, so every derived value
is asserted as a hand-calculated literal, as are the half-built, damaged,
maximum and cube-root-boundary cases. Determinism is checked over 45
growth and temperature combinations. The declared flooring is pinned
rather than hidden: a body whose mass floors to zero advances its counter
for no material, granting no structure because none exists either way.

Omitted physics is a documented model limitation, not a modifier. Nothing
here is balance, and no organism yet develops. Native Release, clang-tidy
analysis, ASan and format checks pass 18/18; every existing golden and
fingerprint is unchanged. Linux CI has not run yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-09-22 21:48:24 -04:00
co-authored by Claude Opus 5
parent 64a12c4dfc
commit 3f86dada0e
11 changed files with 703 additions and 6 deletions
+48
View File
@@ -434,3 +434,51 @@ 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.