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:
+29
-2
@@ -7,7 +7,7 @@ persistent simulation server. The founding vision remains unchanged.
|
||||
## Completed implementation
|
||||
|
||||
- Vision, architectural pillars, risks, open-question register, architecture
|
||||
diagrams, biological contracts, engineering constitution and 35 ADRs.
|
||||
diagrams, biological contracts, engineering constitution and 36 ADRs.
|
||||
Proposed/deferred choices remain distinct from accepted proof decisions.
|
||||
- M0–M4 task breakdowns with dependencies, acceptance evidence and risks,
|
||||
plus M5–M14 gates in [ROADMAP.md](ROADMAP.md).
|
||||
@@ -61,7 +61,7 @@ for the bounded proof; the general production ECS remains a later measured choic
|
||||
|
||||
| Priority | Work | Completion evidence |
|
||||
|---|---|---|
|
||||
| 1 | M4.1 cohort state and ownership | Genome, lineage, counts, age, reserves, residuals and ownership made explicit |
|
||||
| 1 | M4.2 collapse active individuals | Transfer IDs and reserves into one cohort atomically, with exact ledger conservation |
|
||||
| 2 | Revisit the ADR-0031/0032 reproduction cost model | Reproduction is affordable only at the genome schema's floor; decide whether that is intended before M4 builds cohorts on it |
|
||||
| Delivery gate | Add/update the dev workload when a deployable increment needs it; Argo is ready | Observe Job/pod completion separately from image publication; no World0 changes |
|
||||
|
||||
@@ -292,3 +292,30 @@ logout treatment, species/extinction rules and multicellular transition remain
|
||||
open decisions. Renderer/networking remain later milestones. Deployment
|
||||
availability does not complete M7/M8: fenced ownership, durable outcomes, backup
|
||||
restore and world-version migration require their own implementation/fault tests.
|
||||
|
||||
M4.1 opens M4 (ADR-0036) by defining the tier 2 record and who may act on it, and
|
||||
nothing else: there is no collapse transaction, no population advance, no
|
||||
materialization and no habitat geometry. A `Cohort` is validated on construction
|
||||
and never mutated afterwards. Age classes each carry their own count and their own
|
||||
reserve, so the record holds a distribution rather than the mean the milestone's
|
||||
named risk warns about; within a class members are indistinguishable, which is the
|
||||
record's declared resolution and a stated loss rather than a hidden one. No
|
||||
accessor returns a mean. Totals are summed from the classes instead of stored
|
||||
beside them, following the lineage archive's rule that a second tally is a thing
|
||||
that can disagree. Lineage is deliberately not a field: ancestry is resolved from
|
||||
the genome through the archive, so a cohort cannot contradict it or invent
|
||||
parentage from membership. Residuals are integer numerators over a declared scale,
|
||||
strictly below one member, and are never added to a count.
|
||||
|
||||
Ownership is enforced rather than described. `CohortRegistry` admits at most one
|
||||
record per habitat and genome, so ECOLOGY_MODEL's "no inventory is spendable in
|
||||
two tiers" is unrepresentable rather than forbidden, and replacement is refused
|
||||
under a different worker, an older epoch, or a changed habitat or genome. Epochs
|
||||
make a stale writer fail locally and say nothing about fencing between workers,
|
||||
which stays M7 and M10. The approximation bound is carried and never computed:
|
||||
M4.5 measures resolution equivalence, and carrying a bound is not meeting one.
|
||||
Nothing is serialized, so `schemas/population-v1.md` pins field meaning and
|
||||
invariants rather than a byte layout. All nine construction and registry guards
|
||||
were confirmed load-bearing by removing each one and observing the suite fail.
|
||||
Native Release, analysis, ASan and formatting passed 34/34; Linux CI has not run
|
||||
yet.
|
||||
|
||||
Reference in New Issue
Block a user