M11.1: time-based rate conversion (ADR-0099, segment 1)
Foundation / checks (deploy) (push) Successful in 3m27s
Foundation / checks (ecs) (push) Successful in 1m51s
Foundation / checks (client) (push) Successful in 12m31s
Foundation / checks (network) (push) Successful in 13m30s
Foundation / checks (tsan) (push) Canceled after 8m42s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 27m37s
Foundation / checks (postgres) (push) Canceled after 15m9s

Rates are stored per second in their integer base units and converted at the tick
boundary with no carried state: costs round up, capacities down (maintainer decision),
error below one unit per tick. per_second_from_per_tick is the migration's exact inverse
(x20 at 50 ms) and refuses inexact values. New rate-contracts test. No biology uses it
yet; genome v2, development v2 and process fields follow. Refresh the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-09 12:50:54 -04:00
co-authored by Claude Opus 5.5
parent 961b3e3c2f
commit a4c6181540
9 changed files with 293 additions and 4 deletions
+7 -2
View File
@@ -15,8 +15,13 @@ ADR-0098 records the maintainer's decisions for the first playable cellular loop
- **Birth cost:** a first bud fundable within a session (a tunable playtest target).
- **Friend recognition:** deferred.
Next is 11.1's ratified engineering half: migrating biological rates from per-tick to
time-based units (ADR-0089).
11.1's ratified engineering half, time-based biological rates, is under way (ADR-0099;
the maintainer chose directional rounding):
- **Segment 1 (done):** `accounting/rates.hpp` converts a per-second rate to a per-tick
amount without saved state. Costs round up and capacities down, so rounding never
favours the organism. The migration's exact ×20 inverse refuses inexact values.
- **Segments 2–3 (next):** genome schema v2, development version 2, and the process and
checkpoint fields, with unchanged 50 ms goldens.
Open from M10 (BACKLOG):
- the maintainer's native-client observation, moved to the later 2k drill;
@@ -0,0 +1,84 @@
# ADR-0099: Time-based biological rates
## Status
Accepted for M11.1 (2026-10-09). The maintainer ratified the direction on 2026-10-04
(ADR-0089) and chose directional rounding on 2026-10-09. Segment 1 implements the
conversion. Segments 2 and 3 migrate the genome, development and process fields
listed below.
## Context
Biological and environmental rates are stored per simulation tick:
- genome v1 `micrometres_per_tick` and `femtograms_per_tick`;
- development and metabolism maintenance, movement and intake per tick;
- the feeding decomposition limit;
- the environmental community's decay caps.
The 50 ms tick therefore fixes biological speed in real time. ADR-0089 ratified rates
per unit time, converted deterministically at each tick, with an explicit precision
contract and a versioned migration that preserves 50 ms behaviour.
## Decision
- **Unit.** A rate is an unsigned 64-bit integer **per second**, in its existing base
unit: pJ, fg or um. No fixed-point fraction is added. The base units are already
tiny (pJ, fg) relative to any organism's budget, so one base unit per second is
precision enough.
- **Conversion.** At the simulation tick, an amount is
`per_second * tick_microseconds / 1'000'000`, computed as whole seconds plus the
fractional part. No intermediate exceeds 64 bits, and overflow is an error, never a
wrap (`accounting::per_tick`).
- **Rounding** (maintainer decision): it never favours the organism.
- Capacities, limits, speeds and intake round **down**.
- Costs (maintenance, movement, construction) round **up**.
- No remainder is carried, so no new state is saved. The error is below one base
unit per tick per rate, and always against the organism.
- **Tick bounds.** 1 us to 1 s.
- **Exactness at 50 ms.** A per-tick value `v` migrates to `20 v` per second exactly
(`per_second_from_per_tick`). At 50 ms it converts back to `v` under either rounding,
so migrated behaviour is unchanged. The migration refuses any value that has no exact
per-second form at its recorded tick, and never rounds it.
- **Where conversion happens.** Only at the boundary where a rate becomes a per-tick
amount for the step being simulated: the metabolic budget, the consumer
configuration, the decomposition limit and the decay caps. Stored records hold
per-second values.
### Migration (segments 2 and 3)
- **Genome.** Genome schema v2 declares `micrometres_per_second` and
`femtograms_per_second`. A v1 record is never rewritten: it stays as historical
provenance (GENOME_MODEL), and reading it converts at the recorded 50 ms quantum.
- **Development and processes.** Development version 2 and the process configurations
carry per-second rates. Their checkpoint formats take new versions, and older
versions are migrated at load at the checkpoint's own `tick_microseconds`.
- **Goldens.** Each goldened output must be bit-identical at 50 ms before and after.
Any golden that changes is a defect in the migration, never a reason to replace the
golden.
- **Dev world.** The upgrade uses the existing clone, migrate, compare and approve
procedure. World0 is not involved.
## Alternatives considered
- **Carried remainders** (as `integrate_energy` does for incident energy, ADR-0050):
exact over time, but a saved remainder per organism per rate, with a larger
checkpoint migration. Rejected by the maintainer for M11.
- **Rates per millisecond, or a fixed-point fraction:** more precision than the base
units need, and more overflow surface.
- **Changing only the unit labels:** would leave the 50 ms coupling in place.
## Benefits
- A tick change becomes a reviewable change of rounding, not a silent rescaling of
biology.
- No new saved state; conversion is deterministic and checked for overflow.
- Rounding never creates free energy or matter for an organism.
## Costs and risks
- At a tick that does not divide a rate, an organism pays slightly more and takes in
slightly less than the exact rate, by under one unit per tick. Integer floors already
stop a very slow rate (below one unit per tick) from acting at all as a capacity.
For a cost, the same rate charges one unit per tick. Both are deliberate and bounded.
- The rate fields must be converted exactly once, at the boundary. Converting twice,
or not at all, would rescale biology. The goldens at 50 ms are the guard against
this.
## Consequences
- Segment 1: `accounting/rates.hpp` (`per_tick`, `exact_per_tick`,
`per_second_from_per_tick`) and the `rate-contracts` test.
- Segments 2 and 3 migrate the fields above, with new versions and unchanged 50 ms
goldens.
+1
View File
@@ -98,6 +98,7 @@ design. No unadopted candidate is a link dependency of the proof.
- [ADR-0084: Engineering UI toolkit](0084-engineering-ui-toolkit.md) - Dear ImGui 1.92.9b pinned (M9.8a) and integrated as the engineering client overlay with toolkit-first input routing (M9.8c).
- [ADR-0090: M10 QUIC transport](0090-m10-quic-transport.md) - msquic 2.6.2 with OpenSSL 3.5.9 LTS (TLS 1.3 only) from pinned sources on Windows and Linux; DATAGRAM frames for superseding state, streams for reliable actions; M9 TLS/TCP kept as dev fallback; owned impairment relay; exact CA pinning due in 10.2b.
- [ADR-0099: Time-based biological rates](0099-time-based-biological-rates.md) - rates stored per second in their integer base units, converted at the tick boundary with no carried state; costs round up and capacities down (maintainer); exact x20 migration at 50 ms, inexact values refused; genome schema v2, development v2 and process formats follow.
- [ADR-0098: M11 first cellular loop decisions](0098-m11-first-cellular-loop-decisions.md) - maintainer decisions for the first playable loop: budding (parent keeps control, one funded wildlife bud); funded in-life mutation from seeded candidates; exact-copy heredity with no NPC mutation in M11; logout lingers frozen but vulnerable, then suspends; resume in place or nearest valid spot within a bounded radius; absorption plus engulfment by contested size ratio; birth reachable within a session (tunable); friend recognition deferred.
- [ADR-0097: M10 load and abuse qualification](0097-m10-load-and-abuse-qualification.md) - only evolution-dev reference-worker runs qualify; one multi-client evo-load tool with per-client distributions; a load governor over per-tick work (p95 window of 40 ticks) and tick debt refuses grant logins, then sheds replication radius and cadence in 3 levels with hysteresis (tickets still admitted); abuse suite of fuzz, floods, slow peers, storms and lease loss.
- [ADR-0096: M10 probe handoff](0096-m10-probe-handoff.md) - EXPERIMENT durable probe records with one owning region and a conserved test inventory; fenced prepared/staged/committed/aborted transfers; signed single-use transfer tickets; protocol v4 offers, redirects and ghosts; recovery sweep (schema v14) and replay guard proven by a two-process fault matrix.
+19
View File
@@ -5353,3 +5353,22 @@ Executed:
Not run: an RDP display-scale check. Under RDP the logical height drives the scale, the
same as on a local display.
## 2026-10-09 — M11.1 time-based rates, segment 1 (ADR-0099)
`accounting::per_tick`, `exact_per_tick` and `per_second_from_per_tick` were added,
with a new `rate-contracts` test. The test covers:
- exact ×20 migration and round trip at 50 ms, under both roundings;
- directional rounding at an inexact tick, bracketing the exact amount one unit apart;
- sub-unit rates;
- tick bounds;
- the largest rate;
- overflow;
- refusal of an inexact migration.
Executed:
- WSL `linux-debug` and `linux-asan`: `rate-contracts` and `ledger-contracts` passed.
- clang-tidy 19 (`linux-analysis`): clean.
- Windows `debug`: 61/61.
No biology uses the conversion yet, so no golden is affected.