Keep a distribution, because a mean cannot say who survives

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>
This commit is contained in:
dingo
2026-09-24 06:14:07 -04:00
co-authored by Claude Opus 5
parent 72ed03f4dd
commit 1c8b292147
11 changed files with 1045 additions and 2 deletions
+58
View File
@@ -860,3 +860,61 @@ lifetimes mean a run's mean lifetime is not computable from `lived_ticks` alone
and no test asserts one. Across a run the archive now ends holding living
carriers, which is accurate about what was observed and is not a claim that
anything persists; nothing is serialized.
## M4.1 cohort state and ownership
Executed on this Windows host (2026-09-24): Release configure, build and `ctest`
34/34; the analysis preset (clang-tidy 19, warnings as errors) built clean; the
ASan preset configured, built and ran 34/34; `clang-format` 19.1.5 reported no
violations. All four checks ran and passed on the committed tree. No Clang or GCC
compile happens on this host, so Linux CI remains the first result for the new
`evo::ecology` library.
`evo-cohort-tests` covers six properties: that a cohort keeps exactly the fields
it was given, that totals equal the summed classes, that two cohorts with
identical totals but different structure are distinguishable, that every
construction invariant is rejected by its own named error, that one habitat and
genome holds one record, and that only the recorded owner under a current epoch
may replace it. A sixth checks that a cohort names a genome the archive resolves
ancestry for without storing that ancestry.
Every guard was confirmed load-bearing rather than assumed. Each of the nine was
removed in turn and the suite rebuilt and rerun: the duplicate, stale epoch, wrong
owner, unowned reserve, residual bound, class ordering, empty class and class
range guards each produced a failing run, and removing the overflow guard fails to
compile, because the running totals then have no reader and the Release build
treats that warning as an error. An earlier attempt at this sweep reported all
nine as not load-bearing; that result was false and was discarded. The harness
wrote to `/tmp`, which Git Bash and PowerShell resolve to different directories,
so the mutation script was never found and the source was never modified. The
sweep was rerun against an absolute path.
Two defects in my own test code were found and fixed before the suite was trusted.
The single-argument `CHECK` macro split on the comma inside a braced initializer
such as `Owner{11, 2}`, which is a compile error rather than a silent one, and the
macro is now variadic. More seriously, the rejection tests originally asserted on
`.error()` alone, which is undefined when the call unexpectedly succeeded and would
have let a removed guard pass quietly; they now check the failure first through a
`refused` helper. A regex rewrite applied to make that change spanned lines and
corrupted several positive assertions, so the test file was rewritten rather than
patched.
Coverage limits. Nothing here is serialized, so `schemas/population-v1.md` pins
field meaning and invariants and there is no encoder, no round trip and no
migration to test. The approximation bound is carried and never computed or
checked, so no test asserts that aggregation is faithful; that is M4.5.
Conservation between a cohort and the rest of the world is not asserted, because
this type holds an inventory without participating in any transfer. Ownership is
tested as a single-process invariant only: epochs make a stale writer fail locally
and nothing here exercises fencing between workers, which is M7 and M10. Negative
reserves are not representable at all, since every quantity is unsigned, so what
the suite rejects instead is a declared state that would require one, and two
static assertions record that the underlying types are unsigned. `max_cohorts` is
enforced but not exercised at its limit, since installing 4,096 records would add
nothing to what the duplicate and lookup tests already establish.
No existing contract changed. The proof golden `d61ad5bf0c928c76`, the ecosystem
fingerprint `2cd4a15f9fbe9949`, the ensemble fingerprint `5ec59d390909b526` and
the frozen genome fixture are all unchanged, and the other 33 tests pass
untouched. No deployment manifest or image pin changed. Linux validation is
pending; no Gitea result is claimed since `b01a824`.