Keep the phenotype wire-stable: rate period on the budget, not the phenotype
Foundation / checks (deploy) (push) Successful in 3m28s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m43s
Foundation / checks (network) (push) Successful in 13m32s
Foundation / checks (tsan) (push) Successful in 7m48s
Foundation / checks (checks) (push) Successful in 32m55s
Foundation / checks (postgres) (push) Successful in 46m26s
Foundation / postgres-tools (push) Successful in 1m41s
Foundation / server-image (push) Successful in 4m13s
Foundation / image (push) Successful in 2m35s

CI run 136 failed network: Phenotype::rate_microseconds (added with development version
2) is not carried by either session protocol, so the organism view no longer re-encoded
canonically. The phenotype keeps its replicated shape; the period follows from the
development version (development_rate_microseconds) and MetabolicBudget carries it.
No protocol change; first-bud times unchanged. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-09 16:47:23 -04:00
co-authored by Claude Opus 5.5
parent 51cf23dbc9
commit 93e1ab08ae
9 changed files with 48 additions and 21 deletions
+5 -3
View File
@@ -126,9 +126,11 @@ contract and a versioned migration that preserves 50 ms behaviour.
## Development version 2 and the first bud (2026-10-09)
The maintainer chose to set the birth-cost target now and tune it in playtests
(ADR-0098 decision 7).
- **Development version 2** is defined per second. Phenotype and budget rates carry
their period (`rate_microseconds`: 50 ms for version 1, 1 s for version 2), and the
M2 fixture adapters accept only version 1.
- **Development version 2** is defined per second. The rate period follows from the
development version (`development_rate_microseconds`: 50 ms for version 1, 1 s for
version 2), and the metabolic budget carries it as `rate_microseconds`. The phenotype
stays as it was, because it is replicated unchanged on both session protocols. The M2
fixture adapters accept only version 1.
- **Its constants are tunable values, not locked rules:**
- maintenance 10 and membrane upkeep 15 pJ/s per 1000 fg, a quarter of version 1's
per-second equivalent;
+20 -2
View File
@@ -5426,8 +5426,9 @@ Executed:
## 2026-10-09 — M11.1 development version 2 and the primitive founder (ADR-0099)
Development version 2 is defined per second. Phenotype and budget rates carry
`rate_microseconds`, and the M2 fixture adapters refuse anything but version 1.
Development version 2 is defined per second. The rate period follows from the
development version (`development_rate_microseconds`), and the budget carries it as
`rate_microseconds`. The M2 fixture adapters refuse anything but version 1.
`bud_funding_seconds` and `primitive_founder` were added.
`development_v2_and_the_first_bud` checks:
- the hand-calculated per-second phenotype and budget;
@@ -5444,3 +5445,20 @@ Executed:
- clang-tidy 19: clean, after a zero-surplus guard and value reads in the test.
- The 18 Postgres suites: passed.
- Windows `debug`: 61/61.
## 2026-10-09 — CI run 136 network failure: the phenotype stays wire-stable
CI run 136 (`51cf23d`) failed `network` at the organism-view canonical re-encoding
(`network_protocol.cpp:162`). The cause was `Phenotype::rate_microseconds`, added with
development version 2. Both session protocols encode phenotypes field by field, so the
period did not survive a round trip. My local checks had not built the network presets.
Fix: the phenotype is restored to its replicated shape. The rate period follows from
the development version (`development_rate_microseconds`), and `MetabolicBudget`,
which is not replicated, carries it. No protocol change; first-bud times unchanged.
Executed:
- WSL `linux-debug` 61/61 and `linux-asan` 61/61.
- WSL `network-clang` 65/65 and `quic-linux` 68/68.
- clang-tidy 19: clean.
- Windows `debug` 61/61, `quic` 5/5, `client-network` 15/15.