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>
30 lines
1.8 KiB
Markdown
30 lines
1.8 KiB
Markdown
# Architecture decision records
|
||
|
||
Locked requirements outrank these records. Review architecture, ADRs, public
|
||
contracts, tests, then implementation. Stop expanding implementation on conflict.
|
||
|
||
**Adopted for proof** applies only to the bounded initial headless slice.
|
||
**Proposed** recommends without adopting a dependency. **Deferred** requires a
|
||
named experiment. Later **Accepted** and **Superseded** preserve rationale.
|
||
Proof choices do not silently settle gameplay or production infrastructure.
|
||
|
||
Records 0001–0015 cover language, build, dependencies, tests/benchmarks, ECS,
|
||
ticks, randomness, serialization, units, errors, threads, logging, PostgreSQL,
|
||
messaging and metrics. 0016–0019 cover durability/ownership, networking/security,
|
||
infrastructure and voxels. 0020 scopes Gitea delivery and the stateless dev Job.
|
||
Each record has the eight required sections.
|
||
0021 authorizes the opt-in ECS comparison only, not a production dependency.
|
||
0022 adopts the bounded sequential lifecycle-command scheduler for the proof.
|
||
0023 defines local periodic neighborhood queries and a measured linear baseline.
|
||
0024 adopts finite, typed energy/matter inventory transfers for M2.1.
|
||
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
|
||
boundary. Candidate performance and binary-size comparisons are hypotheses until
|
||
benchmarked. Primary sources were reviewed during the initial September 2026
|
||
design. No unadopted candidate is a link dependency of the proof.
|