Add funded reproduction with retained lineage identity
Close the M2.5 fixture cycle. A bounded list of trusted reproduction intents runs after feeding and before decomposition, so a consumer can fund offspring from what it ingested and a process terminated in that tick cannot reproduce. The intent names a withdrawal from the parent reservoir; a fixed construction fraction endows the child and the remainder becomes real heat and waste. Nothing is credited from outside the community, so conserved totals are unchanged by a birth. Reserved slots are pre-allocated at creation, so a birth never grows the ledger and a full community rejects rather than funding a smaller child. Slots never return to the unborn state, so process identities are never reused, and a parent reference plus origin tick outlive both organisms and survive decomposition. A child duplicates the configuration of its parent because no genome exists yet; this is duplication, not heredity. Default zero capacity leaves the M2.4 reservoir layout and every existing result unchanged, including golden d61ad5bf0c928c76. Native Release, clang-tidy analysis, ASan and format checks pass; Linux CI has not run for this increment yet. This defines no reproductive strategy, fecundity rule, mutation model, gestation, spatial placement or account ownership. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
+4
-1
@@ -63,7 +63,10 @@ M2.3 now supplies this bounded shared ownership and ingestion fixture. M2.4 must
|
||||
retain remaining inventory on death and implement explicit corpse/decomposition
|
||||
flows, rather than relying on M2.3's zero-inventory depletion trigger.
|
||||
M2.4 now implements that terminal-inventory and bounded-return contract. M2.5
|
||||
must settle offspring identity and funding before adding reproductive operations.
|
||||
now supplies funded budding, bounded pre-allocated slot capacity and retained
|
||||
parent/origin identity (ADR-0028); offspring are paid for out of parent inventory
|
||||
and no trait varies between generations. M2.6 must exercise the whole cycle over
|
||||
seeded long runs; a closed conservation proof is not yet an interesting ecology.
|
||||
|
||||
## M3 — Genome v0.1
|
||||
|
||||
|
||||
+19
-5
@@ -1,13 +1,13 @@
|
||||
# Project status and next steps
|
||||
|
||||
Updated 2026-09-19. The repository contains an engineering foundation and a
|
||||
Updated 2026-09-21. The repository contains an engineering foundation and a
|
||||
deterministic headless proof. It does not yet contain cellular gameplay or a
|
||||
persistent simulation server. The founding vision remains unchanged.
|
||||
|
||||
## Completed implementation
|
||||
|
||||
- Vision, architectural pillars, risks, open-question register, architecture
|
||||
diagrams, biological contracts, engineering constitution and 27 ADRs.
|
||||
diagrams, biological contracts, engineering constitution and 28 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,8 +61,8 @@ for the bounded proof; the general production ECS remains a later measured choic
|
||||
|
||||
| Priority | Work | Completion evidence |
|
||||
|---|---|---|
|
||||
| 1 | M2.5 funded reproduction contract | Atomic parent/offspring investment, non-reused identity and explicit ancestry without inherited account power |
|
||||
| 2 | M2.6 headless energy-cycle fixture | Complete capture/feeding/reproduction/decomposition cycle, seeded million-tick ecosystem runs and diagnostics |
|
||||
| 1 | M2.6 headless energy-cycle fixture | Complete capture/feeding/reproduction/decomposition cycle, seeded million-tick ecosystem runs and diagnostics |
|
||||
| 2 | M3.1 immutable genome schema and ancestry | Versioned developmental capability data replacing M2.5's duplicated configuration |
|
||||
| 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 |
|
||||
|
||||
M1.6 now implements [the sequential scheduler contract](architecture/SCHEDULER_CONTRACT.md):
|
||||
@@ -125,7 +125,21 @@ decomposition with all earlier phases. Default zero decay preserves earlier
|
||||
fixture behavior. This is not death-cause biology, microbial chemistry, corpse
|
||||
scavenging, persistent lineage history or a database-backed world.
|
||||
Native Release, analysis, ASan and formatting passed, and all four jobs in Gitea
|
||||
run 1417 passed. M2.5 funded reproduction is the next increment.
|
||||
run 1417 passed.
|
||||
|
||||
M2.5 adds funded budding (ADR-0028). A bounded list of trusted reproduction
|
||||
intents runs after feeding and before decomposition, so a consumer can fund
|
||||
offspring from what it ingested and a process terminated in that tick cannot
|
||||
reproduce. The intent names a withdrawal from the parent; a fixed construction
|
||||
fraction endows the child and the remainder becomes real heat and waste. Reserved
|
||||
slots are pre-allocated at creation, so a birth never grows the ledger and a full
|
||||
community rejects rather than funding a smaller child. Process identities are
|
||||
never reused and a parent reference plus origin tick outlive both organisms.
|
||||
A child duplicates its parent's configuration because no genome exists yet; this
|
||||
is duplication, not heredity. Default zero capacity leaves every M2.4 result and
|
||||
the particle goldens unchanged. Native Release, analysis, ASan and formatting
|
||||
passed; Linux CI for this increment has not run yet. This is not a reproductive
|
||||
strategy, fecundity rule, mutation model or funded founder admission.
|
||||
|
||||
Before biology, resolve the relevant heredity and energetic contracts rather
|
||||
than treating proof particles as organisms. Exact game tick rate, NPC mutation,
|
||||
|
||||
@@ -0,0 +1,128 @@
|
||||
# ADR-0028: Funded reproduction and retained lineage identity
|
||||
|
||||
## Status
|
||||
|
||||
Adopted for the M2.5 synthetic community fixture. No genome content, mutation,
|
||||
player account, control grant, spatial placement or gestation model is selected.
|
||||
Lineage identity here is an opaque parent reference, not the M3.1 genome record.
|
||||
|
||||
## Context
|
||||
|
||||
M2.1-M2.4 conserve inventory through capture, growth, feeding, terminal events
|
||||
and bounded decomposition. No operation creates an actor, so every community
|
||||
decays monotonically and M2.6's long-run ecology fixture cannot observe anything
|
||||
but extinction. Reproduction is the missing transfer in ENERGY_MODEL's table.
|
||||
|
||||
Offspring must be funded. A child credited from nothing would break conservation;
|
||||
a child credited by the host would make founder admission implicit. ADR-0024's
|
||||
ledger fixes its reservoir set at construction and exposes no append operation,
|
||||
so actor creation cannot allocate storage mid-run without reopening that contract.
|
||||
|
||||
## Decision
|
||||
|
||||
Extend `FeedingCommunity::advance` with a fourth bounded span of immutable
|
||||
`ReproduceIntent{sequence, parent, investment}` records. Like FeedIntent these are
|
||||
trusted co-located fixture intentions, not client commands or autonomous decisions.
|
||||
Admit at most `max_consumers` per tick, require nonzero unique host sequences,
|
||||
sort by sequence and permit at most one intent per parent per tick.
|
||||
|
||||
`ReproductionConfig{capacity, construction_per_thousand, minimum_endowment}` is
|
||||
fixed at `create`. Capacity reserves that many additional consumer reservoirs
|
||||
after the configured consumers and before waste. Configured consumers plus
|
||||
capacity must not exceed `max_consumers`. Capacity defaults to zero, so existing
|
||||
fixtures keep an identical reservoir layout, waste index, action sequence and
|
||||
golden results. Reproduction is intent-driven; a tick without intents is a M2.4 tick.
|
||||
|
||||
Process state becomes unborn, active or corpse. Reserved slots begin unborn: they
|
||||
hold an empty reservoir, never act, are never valid feeding targets, are not
|
||||
corpses and are not decomposed. `active(id)` is false for unborn and corpse alike;
|
||||
`corpse(id)` and the ancestry queries reject a reserved slot with a distinct
|
||||
`unborn_actor` error rather than reporting an empty corpse. Reproduction allocates the
|
||||
lowest-numbered unborn slot. A slot never returns to unborn, so IDs are never
|
||||
reused and a dead child's identity persists exactly as ADR-0027 requires.
|
||||
|
||||
The intent names the withdrawal from the parent reservoir, mirroring feeding's
|
||||
bite semantics. A fixed `construction_per_thousand` fraction splits it with the
|
||||
same overflow-safe quotient decomposition: the quotient endows the child, the
|
||||
energy remainder goes to heat and the matter remainder goes to waste. Construction
|
||||
overhead is real inventory, not rounding loss. A value of 1000 endows everything;
|
||||
0 sends the whole investment to heat and waste and therefore always fails the
|
||||
endowment floor unless that floor is zero. No fractional entitlement is carried
|
||||
between reproductions.
|
||||
|
||||
Reject the whole tick when the parent is not an active consumer, when the
|
||||
investment is zero or exceeds the parent's balance, when no unborn slot remains,
|
||||
or when the resulting endowment does not meet `minimum_endowment` on every
|
||||
channel. Capacity exhaustion is backpressure: it rejects, it never grants a free
|
||||
or reduced offspring. The producer cannot reproduce in this increment; capture is
|
||||
its funding path and conflating the two would make an abiotic source a parent.
|
||||
|
||||
A child duplicates its parent's consumer configuration verbatim. With no genome,
|
||||
offspring differ from their parents only in inventory. This is duplication, not
|
||||
heredity, and M3 replaces it with developmental capabilities.
|
||||
|
||||
Record an immutable `parent` and `origin` tick per process. Founders record parent
|
||||
zero and origin zero. Both survive the death of the child and of the parent, and
|
||||
remain readable after decomposition empties the reservoir.
|
||||
|
||||
Tick phases: terminal facts -> producer activity -> ordered feeding -> reproduction
|
||||
-> decomposition -> atomic publish. Reproduction after feeding lets a consumer fund
|
||||
offspring with what it ingested this tick; this is a deliberate fixture choice, not
|
||||
a biological claim about digestion latency. Terminal facts run first, so a process
|
||||
terminated this tick cannot reproduce. Intents validate parents against the state
|
||||
entering the reproduction phase, so a child born this tick cannot itself be a
|
||||
parent, feed, be fed upon or be decomposed until the next tick.
|
||||
|
||||
All phases run on the existing private candidate. Any rejected intent rolls back
|
||||
reproduction, feeding, producer progress, decomposition and diagnostics together.
|
||||
Receipts report the sequence, allocated child ID, endowment and overhead, and are
|
||||
published by noexcept move with the rest of the committed state.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
Appending reservoirs on birth would reopen ADR-0024's fixed opening totals and
|
||||
shift the waste index mid-run, invalidating inspection spans and existing goldens
|
||||
for no benefit at fixture scale. Binary fission would force a decision on parent
|
||||
continuity and control identity that REPRODUCTION_MODEL explicitly leaves open.
|
||||
Charging overhead on top of the investment needs a second bounds check and can
|
||||
overflow a parent that could otherwise afford the child. Eggs, cohorts and
|
||||
broadcast spores require gestation timers and statistical allocation that this
|
||||
increment has no fixture for. Reusing dead IDs would save slots and destroy
|
||||
ancestry. Host-credited offspring would break conservation outright.
|
||||
|
||||
## Benefits
|
||||
|
||||
The energy cycle closes: nutrients fund growth, growth funds feeding, feeding
|
||||
funds offspring, death and decomposition return matter. Offspring are provably
|
||||
paid for, capacity is explicit and bounded, ancestry outlives its organisms, and
|
||||
M2.6 can run a seeded long-run ecosystem that is not a guaranteed decay.
|
||||
|
||||
## Costs
|
||||
|
||||
A fixed pre-allocated slot budget is not a population model; a community cannot
|
||||
outgrow its configured capacity and has no aggregation path until M4. Lowest-slot
|
||||
allocation is deterministic but arbitrary. Whole-community copies per tick remain
|
||||
the correctness baseline. Ancestry is a parent reference and an origin tick, not
|
||||
heredity: nothing is inherited, because nothing heritable exists before M3.
|
||||
|
||||
## Risks
|
||||
|
||||
Do not read this as a reproductive strategy, a fecundity rule or a funded founder
|
||||
admission for a persistent world. Construction overhead, the endowment floor and
|
||||
the post-feeding phase position are synthetic parameters that must be reviewed
|
||||
before any biological tuning, and must not become gameplay by being measured.
|
||||
No account owns a process; a parent reference grants no control and no wildlife
|
||||
ownership. Capacity rejection must never be softened into a reduced endowment.
|
||||
|
||||
## Consequences
|
||||
|
||||
Test hand-calculated endowment and overhead splits, the endowment floor, per
|
||||
channel insufficiency with abundant energy, capacity exhaustion, unborn slots
|
||||
rejected as targets and as corpses, terminated and unknown parents, duplicate and
|
||||
zero sequences, more than one intent per parent per tick, whole-tick rollback
|
||||
including producer progress and decomposition, order permutation equality across
|
||||
seeds, absent ID reuse, ancestry surviving both deaths, construction endpoints,
|
||||
u64 extremes and independently recomputed conservation. Default zero capacity must
|
||||
leave every M2.4 result unchanged. A later process snapshot must serialize states,
|
||||
parents, origins and capacity together; M1's codec serializes none of it. No
|
||||
database, renderer, network or deployment change follows from this record.
|
||||
@@ -20,6 +20,7 @@ Each record has the eight required sections.
|
||||
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.
|
||||
|
||||
Every dependency adoption records exact version/commit and integrity hash,
|
||||
transitive license obligations, maintenance/security review, owner and removal
|
||||
|
||||
@@ -202,3 +202,37 @@ flowchart LR
|
||||
Host terminal events do not define health, starvation, combat, age or player death
|
||||
causes. Corpse scavenging, live-world lineage history, persistence and reproduction
|
||||
remain outside this increment. No physical inventory disappears on death.
|
||||
|
||||
## Implemented M2.5 funded reproduction
|
||||
|
||||
[ADR-0028](../adr/0028-funded-reproduction.md) closes the fixture cycle. A bounded
|
||||
list of trusted `ReproduceIntent` records runs after feeding and before
|
||||
decomposition, so a consumer can fund offspring with what it ingested in the same
|
||||
tick and a process terminated in that tick cannot reproduce at all.
|
||||
|
||||
The intent names a withdrawal from the parent reservoir. A fixed construction
|
||||
fraction in thousandths splits it with the same quotient decomposition feeding
|
||||
uses: the quotient endows the child, the energy remainder becomes heat and the
|
||||
matter remainder becomes waste. Construction overhead is owned inventory, not
|
||||
rounding loss. Nothing is credited from outside the community, so the conserved
|
||||
totals are identical before and after a birth.
|
||||
|
||||
Reserved slots are allocated at creation and hold empty reservoirs until a funded
|
||||
birth activates the lowest-numbered one. Capacity exhaustion rejects the tick; it
|
||||
never funds a smaller child. A slot never returns to the unborn state, so process
|
||||
identities are not reused and a parent reference plus origin tick outlives both
|
||||
organisms and survives decomposition of the corpse.
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
F[Ingested matter and energy] --> R[Parent reservoir]
|
||||
R -->|endowment| C[Child reservoir]
|
||||
R -->|construction overhead| H[Heat]
|
||||
R -->|construction overhead| W[Waste]
|
||||
C -->|next tick| A[Feeding, death and decomposition]
|
||||
```
|
||||
|
||||
A child duplicates the configuration of its parent because no genome exists yet.
|
||||
This is duplication, not heredity, and no trait varies between generations.
|
||||
Reproductive strategy, fecundity, juvenile viability, gestation, spatial placement
|
||||
and account ownership are not defined here. No inventory is created on birth.
|
||||
|
||||
@@ -78,3 +78,17 @@ descendants independent of parent death/logout; arbitrarily long suspension
|
||||
preserves every timer; same-tick death/reproduction ordering; huge spore requests;
|
||||
all suspend/resume crash points; changed habitat; unique control grants and
|
||||
death committed after snapshot. Extinction includes suspended viability.
|
||||
|
||||
## Implemented M2.5 fixture boundary
|
||||
|
||||
[ADR-0028](../adr/0028-funded-reproduction.md) implements funded budding inside
|
||||
the synthetic feeding community only. The parent survives and pays an explicit
|
||||
investment; construction overhead goes to heat and waste; a bounded pre-allocated
|
||||
slot capacity rejects rather than granting free or reduced offspring. Ancestry is
|
||||
a parent reference and an origin tick that survive both deaths.
|
||||
|
||||
This settles none of the contracts above. Binary fission continuity, eggs, cohorts,
|
||||
broadcast spores, gestation, strategy selection, mutation candidates, client
|
||||
intentions, control grants, durable acknowledgment and logout treatment remain
|
||||
open. The fixture has no accounts, so a parent reference grants no ownership and
|
||||
no label. Test processes are not wildlife and do not seed a persistent world.
|
||||
|
||||
@@ -275,3 +275,29 @@ no deployment change.
|
||||
[Gitea run 1417](https://git.aeternalisgames.com/dingo/AEvolution/actions/runs/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.
|
||||
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user